Re: [lwip-members] LWIP_COMPAT_SOCKETS

[Jani Monoses]

Hi Kieran
what you fear is what I intended to do but realised it breaks at least 
the unix simulator.It was one of my overzealous attempts at cleaning the code :)
Out of curiosity why would that be a problem to you?It is because you run
on a platform where these names would clash with system functions right?
But yes the compat flag seems of not too much use maybe that will go away
and the macros will default to lwip_xxx
Jani.

> A couple of weeks ago Jani asked if there was any problem with cleaning up
> the sockets code and removing LWIP_COMPAT_SOCKETS, among other things.
> 
> Were you proposing just removing the flag LWIP_COMPAT_SOCKETS, and
> assuming it was always true, so that the macros that take the place of the
> real socket library calls are always defined to redirect things to the
> lwip socket functions?  This is fine with me, but if you were going to
> rename the lwip socket functions to have the same names as the normal
> socket library functions (so they would be called accept() instead of
> lwip_accept() for example) then I would have a problem.
> 
> ie. Are the functions in socket.c still going to be called
> lwip_<whatever>() rather than <whatever>()?
> 
> Thanks
> 
> Kieran
> 
> 
> 
> _______________________________________________
> lwip-members mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/lwip-members