tiger-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tiger-devel] [RFC] Diferences between 'empty and set' and 'unset' v


From: Javier Fernández-Sanguino Peña
Subject: Re: [Tiger-devel] [RFC] Diferences between 'empty and set' and 'unset' variables
Date: Sat, 20 Sep 2003 17:59:57 +0200
User-agent: Mutt/1.5.4i

On Sat, Sep 20, 2003 at 04:12:40AM +0200, Nicolas François wrote:
> > > -- 08_initdefs_haveallvars_allow_empty_vars.patch ----------------------
> > > What should haveallvars do with variables empty but set?
> > 
> > IMHO it should exit just like if it's undefined. I'm adding your patch but 
> > providing a different error message for the other case. Notice that some
> > tests will not work properly if a variable checked by haveallvars() turns 
> > out to be empty.
> 
> You're right. And there would probably be no variable tested by
> haveallvars which could be empty (not checked).
> 
> BTW, there were an error in my patch. I attach a new patch for
> initdefs (initdefs_haveallvars.diff)

However, this does not work for me, scripts executing haveallvars do not
run because of these changes. I have changed the code (and readded the val
statement). Changes are in CVS, please take a look at them.

Javi

Attachment: pgpJv9NEAHdab.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]