Peter Dufault wrote:
>
> > Peter Dufault wrote:
> >
> > > Firstly, you should get rid of any explicit 32, 31, etc and anything
> > > else tied to the assumed number of bits in an int.
> >
> > You first need to get rid of any code that assumes that siget_t is an
> > (unsigned) integer. Use macros to abstract the access to the new sigset_t
> > so that you don't replace one assumption with the other...
>
> But you want that code to break.
What do you mean?
> Further on you'll see I don't support this (this was a "dramatization"
> of the structure), however, because the typedef ends in "_t" it is
> reserved by POSIX for the implementation.
>
> This is a particularly safe implementation typedef,
> since I don't anticipate uint64_t ever being used in a future specification
> as a different data type.
>
> I don't know about ANSI.
The point is that uint64_t (for example) is not exported to ANSI/Posix
sources. uint64_t is simply undefined/undeclared. My first implementation
used u_int32_t, but I had to change that because it broke build world in a
very early stage.
--
Marcel Moolenaar mailto:[EMAIL PROTECTED]
SCC Internetworking & Databases http://www.scc.nl/
The FreeBSD project mailto:[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
