Re: Compiling mico and warnings.
- From: dhawkins Mines EDU (Dale K. Hawkins)
- To: Kjartan Maraas <kmaraas fib hl no>
- Cc: "gnome-list gnome org" <gnome-list gnome org>
- Subject: Re: Compiling mico and warnings.
- Date: 16 Apr 1998 16:23:39 -0600
Kjartan Maraas <firstname.lastname@example.org> writes:
Crap! I just wrote a very interesting statement about why socket
*file descriptors* should be signed int's. But as I reread this, I
release that has nothing to do with what you asked. IMHO, the
situation you described should not suffer any ill effects at all.
Granted it would be better for everything to be the same (I believe
that bind(2) for example expects an int), but this size is much
smaller than an int.
I did it again. Where are you finding getsock? Do you mean
getsockname? In this case the above still holds.
*NOTE TO SELF*
Please read the post carefully before replying! ;-)
> Are the warnings I get about changed singedness while compiling
> The reason for these warnings seem to be that socket_size_t is defined
> as int
> in mico/include/mico/config.h and getsock expects an unsigned int.
> The warnings disappear when socket_size_t is defined as unsigned int.
> Is this the right thing to do? (Does it even matter?)
> (Trying to get started)
> To unsubscribe: mail email@example.com with
> "unsubscribe" as the Subject.
] [Thread Prev