From: Andreas Vogel <Andreas.Vogel@anvo-it.de>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
Subject: Re: [BUG] GRUBs option parsing needs fixing
Date: Thu, 08 Mar 2012 17:11:28 +0100 [thread overview]
Message-ID: <4F58DA30.7050007@anvo-it.de> (raw)
In-Reply-To: <4F58D23A.5020508@gmail.com>
Am 08.03.2012 16:37, schrieb Vladimir 'φ-coder/phcoder' Serbinenko:
> On 08.03.2012 16:28, Lennart Sorensen wrote:
>> On Thu, Mar 08, 2012 at 04:18:05PM +0100, Vladimir 'φ-coder/phcoder'
>> Serbinenko wrote:
>>> We don't have to recreate whole GNU in GRUB either, we don't write
>>> an OS but a bootloader. In particular having -xfoo for isn't
>>> necessarry and moreover it will conflict with
>>> search -su<UUID>
>> So a 'short' option that looks like a 'long' option?
>>
>> Or is that -s and -u together?
> It's -s and -u together and so -s has no argument. With Andreas
> proposition "u" would be the argument
Btw, that's the POSIX/GNU proposition. ;)
>> Options can get confusing at times?
>>
>>> which is already used in the wild.
>>> The case of --long-option optional argument can be changed
>>> especially taking into account migration from 1.98 but -xfoo is
>>> probably out of the question.
>> I don't see how -xfoo where foo is a parameter for -x can work if you
>> support multiple short options being merged (which seems common in
>> GNU programs).
> You can if when encountering an option needing parameter you parse the
> rest as parameter. But then again optional parameter are tricky.
> Behaviour similar to other GNU is important but compatibility with
> previous version of GRUB is more so, especially when it comes to the
> rarely used features like -xfoo.
That's the big misinterpretation done in the past: without being able to
handle "-xfoo" you'll not be able to handle optional arguments in a
proper way. So it's nothing about using a rarely used feature.
The guys writing the POSIX/GNU recommendation did a great job and they
knew exactly what they proposed and for what reasons.
next prev parent reply other threads:[~2012-03-08 16:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 1:13 Ideas for the future Andreas Vogel
2012-03-05 1:30 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-05 1:35 ` Samuel Thibault
2012-03-05 1:40 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-05 9:23 ` Samuel Thibault
2012-03-05 11:16 ` Andreas Vogel
2012-03-05 12:54 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-05 15:43 ` Andreas Vogel
2012-03-08 13:12 ` [BUG] GRUBs option parsing needs fixing Andreas Vogel
2012-03-08 14:15 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-08 14:32 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-08 15:03 ` Andreas Vogel
2012-03-08 15:18 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-08 15:28 ` Lennart Sorensen
2012-03-08 15:37 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-08 16:11 ` Andreas Vogel [this message]
2012-03-08 15:45 ` Andreas Vogel
2012-03-10 19:50 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-11 0:08 ` Andreas Vogel
2012-03-11 1:01 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-11 1:59 ` Andreas Vogel
2012-03-11 2:15 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-08 15:25 ` Lennart Sorensen
2012-03-08 15:58 ` Andreas Vogel
2012-03-08 15:24 ` Lennart Sorensen
2012-03-08 14:11 ` Ideas for the future Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-08 15:14 ` Andreas Vogel
2012-03-08 15:18 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-05 16:33 ` Andreas Vogel
2012-03-08 14:23 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=4F58DA30.7050007@anvo-it.de \
--to=andreas.vogel@anvo-it.de \
--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 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.