Re: A POSIX and a UTF-8 question

[Daniel Qarras <dqarras@yahoo.com>]

Hi!

> > 1) There is unfortunately a bash-only expression used in RH's shell
> > function library, that is =~. However, this was used only once in
> > device mapper related function so that did not affect me, I just
> > commented it out. YMMV. (I did not find a www description for this
> but
> > it can be at least checked from bash3.1 manual pages what it does.
> 
> That's for extended regular expressions.  That wouldn't be too hard
> to
> support, if we used the system's RE capabilities, although we'd
> probably
> want to do parentheses differently.  However, as you say, it's
> specific
> to bash so isn't that vital.

The bug I filed to RH is already handled. This will not change but...

> > 2) It seems that many RH scripts do something like:
> > 
> > cd /some/path
> > . functions
> > 
> > and in zsh-4.3 as /bin/sh this does not work, it needs to be:
> > 
> > cd /some/path
> > . ./functions
> 
> Right.  I think zsh has always been implemented like that.  We don't
> really want to change it; the standard (IEEE Std 1003.1, 2004
> Edition) says specifically:

...this has been fixed in their CVS.

> I checked on my Fedora system (about Core 4, I think) and the only
> init
> script without a path is network:
> 
>   cd /etc/sysconfig/network-scripts
> 
>   . network-functions
> 
> If it's still there it probably ought to be fixed.

FWIW, I had tons of those in my FC5's ifup-* scripts.

> It would be relatively easy to interpret these in the same fashion as
> some other form of quoting.  However, there's not much
> internationalization in these parts and won't be without a huge
> effort
> and it's not clear it's worth the effort doing anything apart from
> that.

I agree, supporting those $"funny variables" is probably not a huge
win.

Thanks!



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com