Re: [CODE] compile error

From: George Greer (
Date: 10/05/00

On Wed, 4 Oct 2000, Daniel A. Koepke wrote:

>On Wed, 4 Oct 2000, George Greer wrote:
>> Change the 'int s' one to 'socket_t s', it was just an oversight.
>Mine actually.  I thought I caught all the cases where 'int' was used in
>place of 'socket_t' (which was a lot of places in comm.c prior to
>bpl17).  gcc didn't warn.  I should've probably manually changed socket_t
>to some other type to make sure gcc wasn't doing an implicit conversion
>without a warning.
>Odd that it didn't warn, though.

They're probably compatible types under the GCC environment you used.
Borland C under Windows doesn't necessarily have to make them compatible
types.  So Linux could have socket_t=int and not warn, but Borland C would
if socket_t=short int.

George Greer

     | Ensure that you have read the CircleMUD Mailing List FAQ:  |
     |  |

This archive was generated by hypermail 2b30 : 04/10/01 PDT