classpath
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cp-patches] RFC: checking for socklen_t


From: Dalibor Topic
Subject: Re: [cp-patches] RFC: checking for socklen_t
Date: Thu, 05 Jan 2006 05:25:32 +0100
User-agent: Mozilla Thunderbird 1.0.7 (X11/20051013)

Dalibor Topic wrote:
On Mon, Jan 02, 2006 at 03:24:38PM +0100, Andreas Tobler wrote:

Christian Thalinger wrote:

On Sun, 2006-01-01 at 23:42 +0100, Andreas Tobler wrote:

Well, he hasn't yet, but I'll add my comment here.

I'd like to see it as an unsigned int and not an int. Most systems I know use unsigned int for socklen_t. Posix.1g also recommends to use uint32_t for socklen_t.

Well, on this very special OS not even uint32_t is defined.  So i'd vote
for `unsigned int' if you think we should use unsigned.

That's fine with me. uint32_t is more or less 'unsigned int'.



I'll try to wrap up a patch from Kaffe today that uses
AX_CREATE_STDINT.m4 from ac-acrhive from Guido Draheim to declare
those nice C99 types on compilers lacking them. It has served us well in
Kaffe. :)

That should make uint32_t available to any classpath code including the
respective wrapper header.


Now that the ax_create_stdint.m4 patch has been checked in, uint32_t should be trasparently at your service if you include config-int.h.

cheers,
dalibor topic




reply via email to

[Prev in Thread] Current Thread [Next in Thread]