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: Scripting support (PATCH)
Date: Sun, 30 Oct 2005 13:17:13 +0100	[thread overview]
Message-ID: <87oe57jj1y.fsf@student.han.nl> (raw)
In-Reply-To: <200510301255.11617.okuji@enbug.org> (Yoshinori K. Okuji's message of "Sun, 30 Oct 2005 13:55:11 +0200")

"Yoshinori K. Okuji" <okuji@enbug.org> writes:

> On Sunday 30 October 2005 10:45 am, Marco Gerards wrote:
>> Right, I felt it hard to explain the direction I'd like to take on
>> this list.  So I have implemented the core functionality because that
>> definitely has to be right.
>
> I don't know what direction you would like yet. It is hard to figure out all 
> of your ideas from the implementation. I only know that it is differently 
> implemented.

Sure, but I have explained it in detail in the emails I sent to the
list a week ago.  My most important point was that I did not want to
use pcode.

>> > - What are disadvantages in Vladimir's implementation?
>>
>> In my opinion it is not clean enough and does not integrate with GRUB
>> like I would like it to.  And Vladimir's patch was way too hard to
>> maintain when I started working on this a week ago.
>
> Can you elaborate on those points? I still don't understand.

That was about the previous patch Vladimir wrote.  His current patch
is based on my code, AFAICS.

I had a review of his previous ( > 1 week ago) code, and had some
problems with it:

- It was very hard to understand.
- It was all handwritten (later bison was used, which is a good
  thing).
- Poorly documented.
- Little reuse or adoption of existing GRUB code.
- No well known design and execution model.  I just based my design on
  the model bash uses.

>> > - What are disadvantages in Marco's implementation?
>> >
>> > Fewer features are implemented. The kernel is bloated.
>>
>> What do you mean with the kernel is bloated?  My patch moves a lot of
>> responsibility to commands.  I would say it is less bloated.
>
> I mentioned this, because your parser is built into the kernel. This is 
> unnecessary, as the rescue mode does not need fancy features.

It is build into normal mode.  And even much is not put in normal
mode, but in commands like `['.

The thing you see in the kernel is a replacement for the command to
split lines into arguments.  The old code for this was removed.  So
some code was removed and some was added, the end result is about the
same, but more reusable code.

--
Marco




  reply	other threads:[~2005-10-30 12:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-29 21:41 Scripting support (PATCH) Marco Gerards
2005-10-30  5:25 ` Yoshinori K. Okuji
2005-10-30  9:45   ` Marco Gerards
2005-10-30 11:55     ` Yoshinori K. Okuji
2005-10-30 12:17       ` Marco Gerards [this message]
2005-10-30 10:14   ` Marco Gerards
2005-10-30 14:41 ` Vladimir Serbinenko
2005-10-30 16:05   ` Marco Gerards
2005-10-30 16:46     ` Vladimir Serbinenko
2005-10-30 16:59       ` Marco Gerards
2005-10-30 17:15         ` Vladimir Serbinenko
2005-10-30 18:17           ` Marco Gerards
2005-10-31  6:39   ` Yoshinori K. Okuji
2005-10-30 20:49 ` Hollis Blanchard
2005-10-30 21:04   ` Marco Gerards
2005-10-31  6:45     ` Yoshinori K. Okuji
2005-10-31 18:58       ` Marco Gerards
2005-11-01 19:06         ` Marco Gerards
2005-11-01 19:55           ` Yoshinori K. Okuji
2005-11-03 21:58 ` Marco Gerards
2005-11-06 22:26   ` Marco Gerards
2005-11-08  3:38     ` Hollis Blanchard
2005-11-08 18:24       ` Marco Gerards
2005-11-09  6:14         ` Hollis Blanchard
     [not found] <200511010611.jA16B6Bq030884@dell01.dinaserver.com>
2005-11-02  9:37 ` adrian15
2005-11-06 22:13   ` 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=87oe57jj1y.fsf@student.han.nl \
    --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.