Wily Dev wrote: > Until these issues are resolved, it might be advisable to set the > Sock.RaiseExcept property to TRUE, if your program can deal with this sort > of processing. That will force the right error to surface immediately (as > far as I can see, and so it seems in very limited testing). >
Thanks for the compassion about the problem.. I figured it was just me.. Maybe another possible work around is for me to pull in the Freepascal sockets unit into my uses clause.. and call the Connect or Bind procedure first directly from FPC sockets.pp. Use that as a dummy check first.. Then after done checking that.. use the actual synapse bind function. Fpc sockets bind function returns true or false: http://z505.com/cgi-bin/powtils/docs/1.6/idx.cgi?file=bind&unit=sockets Regards, L505 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ synalist-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synalist-public
