[fpc-pascal] why connect is "deprecated"

Marco van de Voort marcov at stack.nl
Tue Apr 16 12:13:42 CEST 2013

In our previous episode, Jonas Maebe said:
> >> Function Connect(Sock:longint;const addr:TInetSockAddr;var
> >> SockIn,SockOut:text):Boolean; deprecated;
> >
> > It was deprecated for two reasons:
> >
> > 1. the format, returntype and parameter typing is at 1.0.x level and  
> > was
> > never updated to 2.0
> > 2. errorhandling is limited to non existent.
> As far as I can see, all errors are returned via inoutres/IOResult in  
> the same way as happens with disk-based IO.

Yes. An attempt is made to map some of the errors to I/O. Anyway, if sb
wants to support and modernize them, I have no problem with that. But that
hasn't happened since 2005-2007 or so.

That would also make it possible to directly map socketerror to
getlastresult/fpgeterrno, instead of caching it in another threadvar.

More information about the fpc-pascal mailing list