On Tue, Apr 15, 2008 at 6:26 AM, Hisham <[EMAIL PROTECTED]> wrote:
> On Mon, Apr 14, 2008 at 5:09 AM, Michael Homer <[EMAIL PROTECTED]> wrote:
> > On Sun, Apr 13, 2008 at 8:03 PM, jan <[EMAIL PROTECTED]> wrote:
> > > On Saturday 12 April 2008 20:06:10 Michael Homer wrote:
> > > > The environment variable takes a space-separated list of flag
> > > > specifications (rather than newline), so it accepts a special syntax
> > > > for the specifications, with ';' instead of a space when listing
> > > > programs to go with a flag. It takes the ugly syntax because it's
> > > > likely to be by far the least common way of using it. The same set of
> > > > flags from above could be applied with:
> > > > USE="+foo -bar +bar;FooBar"
> > >
> > > I'd prefer if colon was used instead. My brain reflexively parses the
> > > semicolon as a statement separator.
> > > USE="+foo -bar +bar:FooBar"
> > We can't use a colon, because that's reserved for /S/Aliens (that
> > *has* to get something that isn't a shell metacharacter). There's not
> > much punctuation left that we can use in a string without it getting
> > mangled by the shell. The other options available are: @#%^&|/ - if
> > one of them would be better I can change it, but I don't really see
> > it.
>
> Any of those (except # perhaps) would be better, because ";" really
> implies 'line separator' for most eyes. I'd say go with @ (it would
> read something "bar flag at FooBar" which kinda makes sense).
That seems reasonable. Done in r3186.
-Michael
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
