From: Marco Gerards <metgerards@student.han.nl>
To: Vladimir Serbinenko <phcoder@gmail.com>
Cc: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Scripting support (PATCH)
Date: Sun, 30 Oct 2005 19:17:49 +0100 [thread overview]
Message-ID: <877jbuhnsi.fsf@student.han.nl> (raw)
In-Reply-To: <4364FFC4.2080401@gmail.com> (Vladimir Serbinenko's message of "Sun, 30 Oct 2005 18:15:48 +0100")
Vladimir Serbinenko <phcoder@gmail.com> writes:
> Marco Gerards wrote:
>
>>Vladimir Serbinenko <phcoder@gmail.com> writes:
>>
>>So the problem with approach #1 is doing double work, less obvious
>>integration with the rest of the parser and memory leakage.
>>
>>
> Of course in real code it would be freed. It was just schemathical
Right, but the other disadvantages remain. So I really want approach
#2 to be used unless it has a clear disadvantage.
--
Marco
next prev parent reply other threads:[~2005-10-30 18:17 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
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 [this message]
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=877jbuhnsi.fsf@student.han.nl \
--to=metgerards@student.han.nl \
--cc=grub-devel@gnu.org \
--cc=phcoder@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox