Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 Aug 2002 14:39:54 -0700
From:      Joe Abley <jabley@automagic.org>
To:        Sheldon Hearn <sheldonh@starjuice.net>
Cc:        "M. Warner Losh" <imp@bsdimp.com>, nbm@mithrandr.moria.org, rizzo@icir.org, arch@FreeBSD.ORG
Subject:   Re: ugliness in rc.* scripts
Message-ID:  <20020821213954.GR92068@felix.automagic.org>
In-Reply-To: <20020821180344.GB33546@starjuice.net>
References:  <20020820232538.A53816@iguana.icir.org> <20020821074819.GA58163@mithrandr.moria.org> <20020821.095252.61131232.imp@bsdimp.com> <20020821180344.GB33546@starjuice.net>

next in thread | previous in thread | raw e-mail | index | archive | help

On Wed, Aug 21, 2002 at 08:03:44PM +0200, Sheldon Hearn wrote:
> On (2002/08/21 09:52), M. Warner Losh wrote:
> 
> > Why not just have
> > 
> >     case -i ${some_config_variable} in
> > 
> > to do the case folding.  This would be a backwards compatible extension:
> 
> I don't think the ugliness involved in the rc scripts justifies any of
> the proposed hack-arounds yet.
> 
> And if you _were_ going to hack around, you'd want to introduce a form
> of parameter expansion that did lower-case transliteration for you, e.g.
> 
> 	${parameter:lc}
> 
> Much more useful, but non-portable.

Non-portability might be tolerable if there was some explicit switch
required to turn on support for the non-portable bits. It's not as
if FreeBSD startup scripts need to be run in many environments with
many different sh's.

If portability is a concern for reasons I am missing, then zsh and
ksh both contain parametere expansion flags for case manipulation.
That line of reasoning leads to quite a different bikeshed, however.

> But I digress.  I don't think the ugliness is ugly enough.

Me neither.


Joe

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020821213954.GR92068>