linux libio status

[Pal Engstad]

Olivier Galibert wrote:
> Conclusion: we're here to help people make programs, not implementing
>             language non-normative politics.
> 

Following this thread, the discussion is on the macro NULL. From the 
Draft working paper it is said:

C.4.2.3 Macro NULL

1 The macro NULL, defined in any of <clocale>, <cstddef>, <cstdio>, 
<cstring>, <ctime>t, or <cwchar>, is an implementation-defined C++ 
null-pointer constant in this International Standard (18.1) 254)

254) Possible definitions include 0 and 0L, but not (void *)0.

Given this, it is evident that the choise is either 0 or 0L. I believe
it should be given in accordance with what fits best with the 
architecture it is on. I.e.: If the target has 32 bit int and 32 bit
pointers, it should be 0. If the target has 64 bit longs and 64 bit 
pointers it should be 0L, and so on.

PKE.