All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Serbinenko <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Scripting support
Date: Sat, 22 Oct 2005 18:03:14 +0200	[thread overview]
Message-ID: <435A62C2.6030408@gmail.com> (raw)
In-Reply-To: <87d5lxtuyt.fsf@student.han.nl>

Marco Gerards wrote:

>Vladimir Serbinenko <phcoder@gmail.com> writes:
>
>  
>
>
>I think we first have to determine:
>
>1) Which commands should be supported.
>  
>
What about 
&& || ! case do done elif else esac fi for function if in then until 
while { } [[ ]]
in scripting engine. I think that time is completely useless. What do 
you think about select?

>2) The smallest subset of commands that should be generated.
>
>  
>
I think
jmp
je/jne
invert (not for last return)
exec
regexp (check if string matches regexp)
push
pop
getelem (get element from list)

should be enough
External commands would be eval and [[
functions can be stored directly by parser

>
>Perhaps the best is to make a list of tokens we need to support.  With
>such list we can determine how to detect them.
>  
>
I think just comparing (after \ one character is not compared) might be 
enough.
; newline ;; && || ! case do done elif else esac fi for function if in 
then until while { } [[ ]]

>Thanks,
>Marco
>
>
>  
>
                                                             Vladimir 
'phcoder' Serbinenko



  reply	other threads:[~2005-10-22 16:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-22 13:59 Scripting support Marco Gerards
2005-10-22 14:46 ` Vladimir Serbinenko
2005-10-22 15:08   ` Marco Gerards
2005-10-22 15:37     ` Vladimir Serbinenko
2005-10-22 15:47       ` Marco Gerards
2005-10-22 16:03         ` Vladimir Serbinenko [this message]
2005-10-22 16:42           ` Marco Gerards
2005-10-22 16:33         ` Marco Gerards
2005-10-28  3:04   ` Yoshinori K. Okuji

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=435A62C2.6030408@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.