All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [Suggestion] LILO-like direct menu item access && scripting
Date: Fri, 11 Feb 2005 20:27:00 +0000	[thread overview]
Message-ID: <87650yonaj.fsf@marco.marco-g.com> (raw)
In-Reply-To: <4208E717.9040205@list.ru> (Serbinenko Vladimir's message of "Tue, 08 Feb 2005 17:21:43 +0100")

Serbinenko Vladimir <serbinenko.vova@list.ru> writes:

> Yoshinori K. Okuji wrote:
>
>>On Monday 07 February 2005 15:43, Serbinenko Vladimir wrote:
>>  
>>
>>>private. The other problem is the mails: the patch is quite big and
>>>is blocked somewhere (I sent it to grub-devel but haven't received).
>>>If somebody is interested he can send me private e-email and I'll
>>>send the patch in private
>>>    
>>>
>>
>>Please don't send it by e-mail here. Is it difficult for you to put the 
>>patch somewhere? If you have no public place yourself, you can use 
>>Savannah.
>>
>>  
>>
> Here it is http://phcoder.narod.ru/bash.diff. I know that it's slow
> hosting but I haven't received the confirmation e-mail from faster one yet

I had a quick look at the patch for now.  Can you please explain in a
new thread how the patch globally works?  I will reply about the other
issues there as well.

There are still some things I would like to know:

- Why does everything happen with strings?

- Why are that many functions duplicated? (for example
  grub_bash_dupstr).

- What is that huge table with operators?  What kind of parser is it?
  I have never seen this in a top-down or bottom-up parser I have
  studied.

- How does the parser in general work?  So can you explain what
  happens when executing a script?  First you load the file.  Do you
  parse it, make pcode of it, run it directly?  How about error
  handling?

Thanks,
Marco




  reply	other threads:[~2005-02-11 20:41 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-07 12:10 [Suggestion] LILO-like direct menu item access Marc-Jano Knopp
2005-02-07 14:43 ` [Suggestion] LILO-like direct menu item access && scripting Serbinenko Vladimir
2005-02-07 17:33   ` Marco Gerards
2005-02-07 23:24     ` Marc-Jano Knopp
2005-02-08 10:25       ` Serbinenko Vladimir
2005-02-08 20:56         ` Marc-Jano Knopp
2005-02-08 21:54           ` Marco Gerards
2005-02-08 21:48       ` Marco Gerards
2005-02-08 22:51         ` Marc-Jano Knopp
2005-02-09 10:21           ` Serbinenko Vladimir
2005-02-10 19:24             ` Yoshinori K. Okuji
2005-02-10 21:51               ` Marc-Jano Knopp
2005-02-11  9:38                 ` Yoshinori K. Okuji
2005-02-11 12:09                   ` Marc-Jano Knopp
2005-02-11 14:34                     ` Serbinenko Vladimir
2005-02-11 16:37                       ` Marc-Jano Knopp
2005-02-11 17:13                         ` Serbinenko Vladimir
2005-02-13 18:25                           ` Marc-Jano Knopp
2005-02-10 21:39             ` Marc-Jano Knopp
2005-02-08 13:20   ` Yoshinori K. Okuji
2005-02-08 16:21     ` Serbinenko Vladimir
2005-02-11 20:27       ` Marco Gerards [this message]
2005-02-11 22:01         ` Scripting Serbinenko Vladimir
2005-02-13 18:56           ` Scripting Marco Gerards
2005-02-13 19:39             ` Scripting Serbinenko Vladimir
2005-02-13 19:54             ` Scripting Hollis Blanchard
2005-02-14 21:39               ` Scripting Marco Gerards
2005-02-15 16:16                 ` Scripting Serbinenko Vladimir
2005-02-15 22:13                   ` Scripting Yoshinori K. Okuji
2005-02-07 17:20 ` [Suggestion] LILO-like direct menu item access Marco Gerards

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=87650yonaj.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.