I'm the FPC devel that deprecated those functions. However if I had my 
way they would have been removed in 2.0.0 (since so much changed then, 
specially for unix, it wouldn't have matters) Other members of the team 
wanted to have a graceperiod. Due to documentation issues of this 
deprecated status, the 2.2.0 removal was not done. 2.2.0 supported the 
"deprecated" directive.

http://wiki.freepascal.org/User_Changes_Trunk#Almost_all_old_1.0.x_socket_unit_functions_have_been_removed

I subscribed to this maillist to answer questions. Bear in mind that I 
don't use synapse though, I ended up with indy10 because it supported 
FreeBSD earlier.

 > And what is recommend instead of socketsh now?

Unit sockets is still supported. Just those functions not. They never 
were in any 2.0.0 version, and there have been problems repeatedly with 
them, mostly when people passed pointers to the formal parameters.

Moreover they were not 100% really backwards compatible to 1.0 in the 
first place (since errorhandling changed too much in the 1.0->2.0 change)

Three kinds of changes are necessary:
- most socket functions will need to get a "fp" prefix (like all other
    *nix FPC functions)
- some socket functions are slightly renamed to match C names
(getsocketoption to getsockopt, and several more)
- It might be necessary to add @ here and there, since the prototypes 
are now C like, and uses pointers instead of untyped VAR parameters.

If you are interested in the how and why of the prefix, read 
http://www.stack.nl/~marcov/unixrtl.pdf most notably paragraph 4.6



------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
synalist-public mailing list
synalist-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synalist-public

Reply via email to