date(1) treats TZ '' differently from unset

On a system where local time is +0100: % (unset TZ; date +%z) +0100 % (TZ= date +%z) + Are you sure this is correct? I would have expected the empty string for TZ to act the same as having that variable unset, or otherwise to produce a warning that TZ was set to a bad value. % date --versio

Re: date(1) treats TZ '' differently from unset

Ed Avis <[EMAIL PROTECTED]> writes: > What does POSIX say about date(1) and the TZ variable? POSIX says that if TZ is unset, "implementation-defined default timezone information shall be used"; see . POSIX does not specify the b

Re: date(1) treats TZ '' differently from unset

On 10 Aug 2003, Paul Eggert wrote: >>% (unset TZ; date +%z) >>+0100 >>% (TZ= date +%z) >>+ >This is a C library issue, not a coreutils issue, since coreutils >simply repeats what the C library tells it. What does POSIX say about date(1) and the TZ variable? -- Ed Avis <[EMAIL PROTECTED]>

Re: date(1) treats TZ '' differently from unset

Ed Avis <[EMAIL PROTECTED]> writes: > On a system where local time is +0100: > > % (unset TZ; date +%z) > +0100 > % (TZ= date +%z) > + > > Are you sure this is correct? This is a C library issue, not a coreutils issue, since coreutils simply repeats what the C library tells it. In many C l