All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Scripting (IMPORTANT!)
Date: Sat, 14 Oct 2006 17:43:50 +0200	[thread overview]
Message-ID: <87y7rirjgp.fsf@xs4all.nl> (raw)
In-Reply-To: <200610141729.26325.okuji@enbug.org> (Yoshinori K. Okuji's message of "Sat, 14 Oct 2006 17:29:26 +0200")

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

> On Friday 13 October 2006 23:03, Marco Gerards wrote:
>> It's good you mention this, because it's exactly the discussion I want
>> to start.  The question here is: How do we want to deal with the
>> `for'?
>>
>> In bash it iterates over all arguments.  The wildcards are expanded by
>> the shell and thus it just has a look at its arguments.  The question
>> here is, do we want to deal with wildcards?  It makes the code more
>> complex and I think there is little gain.
>>
>> For GRUB I think some kind of iterators are more useful.  In that case
>> you can write a module to iterate over certain data.  For example over
>> files, disks, partitions, terminals or whatever.  It leaves the bash
>> syntax, but it is more useful in our case and modular.
>
> If you make this feature only for "for", the behavior would be not intuitive 
> for the user. For instance, if "echo" does not interpret wildcards, we would 
> hear the same question, "Why doesn't this work?", again and again. Also, It 
> sounds really ugly to interpret wildcards in each command.

Ok, that sounds sane.  But it does not address my problem.  How would
one iterate over disks and partitions.  And perhaps other things like
loaded modules, etc.  Personally I do not care a lot about syntax, but
I want the language to be full features so most end users can do what
they want.

--
Marco





  reply	other threads:[~2006-10-14 15:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05 13:41 Scripting (IMPORTANT!) Marco Gerards
2006-10-05 14:19 ` Johan Rydberg
2006-10-05 14:36 ` Johan Rydberg
2006-10-09 12:52 ` tgingold
2006-10-13  2:48 ` Hollis Blanchard
2006-10-13  9:48   ` Marco Gerards
2006-10-13 19:32 ` Yoshinori K. Okuji
2006-10-13 19:52   ` Marco Gerards
2006-10-13 20:13     ` Yoshinori K. Okuji
2006-10-13 21:03       ` Marco Gerards
2006-10-14 15:29         ` Yoshinori K. Okuji
2006-10-14 15:43           ` Marco Gerards [this message]
2006-10-14 15:45             ` Yoshinori K. Okuji
     [not found] <200610051534.k95FYart014206@dell01.dinaserver.com>
2006-10-06  7:50 ` adrian15
2006-10-06 14:28   ` 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=87y7rirjgp.fsf@xs4all.nl \
    --to=mgerards@xs4all.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.