Hi Alan,
ah, that makes it clearer. So, on 32-bits platforms
we have time_t defined as a 4 bytes data type?
I have no easy access to 64-bits Windows, unfortunately,
so I can not test this.
(Something I ought to do is add a test for long long int:
this is not supported by older C compilers and
Hi Werner,
one thing I can think of as the underlying cause, is that Windows uses
bands to print a plot. Or that may the abstraction I know from one
particular GUI toolkit. The trick used there is that you need to
repeat drawing until all bands have been done. But I do not know
if that is the
On 2009-02-20 14:17- trc wrote:
Also for reference from the MSDN documentation - The range of mktime64 and
mkgmtime64 is from midnight, January 1, 1970, UTC to 23:59:59, December 31,
3000, UTC.
That's what I don't understand. A 64-bit time_t allows you a theoretical
range of +/- 2^63 s =
As of revision 9570 I have implemented a new time API for PLplot which
consists of c_configtime, c_plbtime, and c_plctime. These are wrappers (see
src/pltime.c) for the qsastime library routines configqsas, btimeqsas, and
ctime_qsas. These wrappers internally store and use the needed pointer to a
Hi,
The Wingcc printing function uses a Win3.11 API entry point which is
simpler (in all respects) than other APIs windows has for printing. One
side-effect is it leaves the burden of responsibility for certain things
upon the user to ensure all is correct with the printer; consequently you
