No, it's correct. It is non-zero if a DST-(using)- zone is specified.
Certain states (Indiana, Arizona) do NOT use DST. For them,
this value is zero, and the machine makes no attempt to correct
time for DST. For beautiful New Jersey, you do switch, and the
flag to tell the computer to make the switch and is _daylight == 1.
I'm not sure how you find out whether DST is currently active or not,
without parsing the results of the functions. But since the machine
takes care of it for you, why do you care ?
It's November, I'm here in beautiful New Jersey, in the Eastern time
zone. Since it's November, it's Eastern Standard Time. In the summer, it's
Eastern Daylight Savings Time.
There's an enviroment variable called "_daylight" that VC help
describes as:
_daylight - Nonzero value if a daylight-saving-time zone is specified in
TZ setting; otherwise, 0
So it's nozero (read "1") if it is Daylight Savings Time. It's
November, so it is not Daylight Savings Time. So _daylight should be 0 this
time of year, right? Well, its not on 4 NT boxes or 1 Win95 machine here.
It says "1".
!! Fun With Timezones !!