Re: stime.c forcing errno

[Kevin Ryde]

address@hidden (Paul Jarc) writes:
>
> But for mktime/strptime, test for failure afterwards and
> set errno in that case.  Setting it beforehand may not help; since
> these functions are not documented to have any particular effect on
> errno, they might have any effect at all - such as replacing our
> EINVAL with something nonsensical.

I guess it's a possibility.  I'll set it afterwards.

> It would also be ok to test afterwards for localtime/gmtime as well.
> POSIX says they should set errno, but the C standard doesn't, so that
> might be a good idea.

Ok, then I'll go with what I made.