Path: utzoo!utgpu!water!watmath!clyde!ima!haddock!karl
From: karl@haddock.ISC.COM (Karl Heuer)
Newsgroups: comp.lang.c
Subject: Re: Oddities in ANSI 3rd review
Message-ID: <5806@haddock.ISC.COM>
Date: 4 Aug 88 04:09:11 GMT
References: <253@gannet.cl.cam.ac.uk>
Reply-To: karl@haddock.ima.isc.com (Karl Heuer)
Organization: Interactive Systems, Boston
Lines: 14

In article <253@gannet.cl.cam.ac.uk> am@cl.cam.ac.uk (Alan Mycroft) writes:
>2.  4.12.1:  "[In <time.h>] 'struct tm'  ... shall contain *at least*
>     the following members... int tm_sec; ...".
>    However, it would seem that an *implementation* would be non-conforming
>    if it contained more members: ...

Well, a conforming implementation could certainly add members in the reserved
namespace (leading underscore), and it could provide convenient access to them
via a macro "#define tm_usec __tm_extended_usec" which is only defined if the
user has enabled the extensions ("#include <extensions.h>" or whatever).  This
is the same sort of situation that the implementor must face when providing
non-ANSI functions like read().

Karl W. Z. Heuer (ima!haddock!karl or karl@haddock.isc.com), The Walking Lint