On Monday, 1994-07-25  Chris Mcbrien wrote to All about "Compiler Bug"
as follows:

CM> I am using C/Set++ version 2.1 for OS/2.
CM> 
CM> I have been writing a small utility for OS/2 BBS's, when I 
CM> discovered a bug in the compiler.
CM> 
CM> When calling the standard C function LocalTime, I have 
CM> noticed that the structure field StuctName->tm_mon contains 
CM> a value one less than the correct month.
CM> 
CM> Has anybody else seen this?  Am I lossing my marbles?  I 
CM> have confirmed this with a minimal test program, and the 
CM> IPMD.

Hi Chris,

I clipped the following from the C Set ++ library .INF file:

___--------------------------------------------------------- 

 The fields of the tm structure include: 

 Field            Value Stored 
 tm_sec           Seconds (0-61) 
 tm_min           Minutes (0-59) 
 tm_hour          Hours (0-23) 
 tm_mday          Day of month (1-31) 
 tm_mon           Month (0-11;  January = 0) 
 tm_year          Year (current year minus 1900) 
 tm_wday          Day of week (0-6;  Sunday = 0) 
 tm_yday          Day of year (0-365;  January 1 = 0) 
 tm_isdst         Zero if Daylight Saving Time is not in effect;  positive
if Daylight 
                  Saving Time is in effect;  negative if the information is
not available. 
___----------------------------------------------------

So the months of the year are numbered 0-11, not 1-12. This explains
why it seems to be a month earlier than the calendar says. If you use
the asctime() function to convert to ASCII it will convert it
correctly.

Regards

Dave

___
 X KWQ/2 1.2e X I have so much mail, I've sinking in .QWKsand...

--- Maximus/2 2.01wb