From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Pre-alpha scripting engine
Date: Wed, 19 Jan 2005 13:01:40 +0000 [thread overview]
Message-ID: <87oeflwp1n.fsf@marco.marco-g.com> (raw)
In-Reply-To: <41ED6964.9010102@list.ru> (Serbinenko Vladimir's message of "Tue, 18 Jan 2005 20:54:12 +0100")
Serbinenko Vladimir <serbinenko.vova@list.ru> writes:
> Marco Gerards wrote:
>
>>Can you please explain how the parser itself works? What kind of
>>parser is it, something about the scanner perhaps, etc?
> It's two times parser. First time it removes comments and creates
> function list.Then it launches "script_load" function. Real script
> execution is in script_execute.
[...]
Ok. What I would like to see in GRUB is a simple top-down parser.
That makes it really easy for us to maintain it. Here is some more
information about top-down parsers:
http://en.wikipedia.org/wiki/Top-down_parsing
This wikipedia entry is a bit short, but there is a lot of information
you can find about this subject on google.
One other thing I noticed is that is is not GCS conforming. GRUB is
GCS conforming and we want to keep it that way. The GCS the document
that describes our coding style, the way we document changes, etc:
http://www.gnu.org/prep/standards/
But as I said before, the most important thing that needs to be done
is that Okuji agrees with the syntax.
>>How about grub.cfg? It would be nice if it would be possible to embed
>>code there.
> You can just write in grub.cfg
> insmod script
> script <file>
> And there is no mess between scripts and shell(however shell
> functions can be used by scripts...will in alpha)
Ok...
What I would like to see is that scripting would be possible in the
configuration file and that it easily integrates.
Thanks,
Marco
next prev parent reply other threads:[~2005-01-19 13:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1CpUhp-000IYX-00.grub-devel-bounces+serbinenko-vova=list-ru-gnu-org@mx11.mail.ru>
2005-01-14 18:48 ` Pre-alpha scripting engine Serbinenko Vladimir
2005-01-18 18:55 ` Marco Gerards
2005-01-18 19:54 ` Serbinenko Vladimir
2005-01-19 13:01 ` Marco Gerards [this message]
2005-01-19 20:04 ` Yoshinori K. Okuji
2005-01-19 20:48 ` Marco Gerards
2005-01-19 21:48 ` Maurizio Boriani
2005-01-20 17:10 ` Serbinenko Vladimir
2005-01-20 17:56 ` Yoshinori K. Okuji
2005-01-20 18:34 ` Serbinenko Vladimir
2005-01-21 2:26 ` Hollis Blanchard
2005-01-21 17:23 ` Scripting, partitions and filesystems Serbinenko Vladimir
2005-01-21 17:52 ` Device syntax, scripting, " Serbinenko Vladimir
2005-01-23 14:22 ` Pre-alpha scripting engine Yoshinori K. Okuji
2005-01-19 20:59 ` Tomas Ebenlendr
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=87oeflwp1n.fsf@marco.marco-g.com \
--to=metgerards@student.han.nl \
--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.