Marco,

The patch I'm going to propose is to solaris/unxsockh.inc which is platform
specific. It'll include defines from /usr/include/netinet/in.h which are
included in linux/unxsockh.inc but missing in solaris/unxsockh.inc.
I won't include the MSG_NOSIGNAL "HACK". ssfpc.pas/inc has already ifdef's
around MSG_NOSIGNAL and adding another platform is indeed the cleanest
solution.

Ludo


> No emulations. The policy is roughly this:
> - if the constant is supported by most platforms it can be added to a 
> platform independant unit (like sockets) with a "platform;" modifier, 
> and it will not be there or emulated for units that don't support it.
> - if the constant is only supported by one platform it must move to a 
> platform specific unit.
> 
> Actually it is on my todo to further clean up the sockets 
> unit that way, 
> marking OS specific functionality that might not be implemented with 
> Platform;.  Bootstrapping issues prevented large scale adding of such 
> modifiers till now.
> 
> (and actually for a time MSG_NOSIGNAL was not there in 
> FreeBSD either, 
> till a later revision added (documented?) the functionality. 
> So it seems 
> to be not an universal constant)
> 


------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
synalist-public mailing list
synalist-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synalist-public

Reply via email to