Re: [fpc-pascal] Socket error messages

2013-09-24 Thread Michael Van Canneyt
On Tue, 24 Sep 2013, Mark Morgan Lloyd wrote: How does one convert from the numeric value returned by SocketError to the name of the error (specifically, to e.g. EsockEINVAL rather than EsysEINVAL, i.e. to be in line with the definition of functions like fpbind)? use the errors unit. (spe

Re: [fpc-pascal] Socket error messages

2013-09-24 Thread Mark Morgan Lloyd
How does one convert from the numeric value returned by SocketError to the name of the error (specifically, to e.g. EsockEINVAL rather than EsysEINVAL, i.e. to be in line with the definition of functions like fpbind)? > use the errors unit. (specific for unix) > > It has a functiun strerror()

Re: [fpc-pascal] Socket error messages

2013-09-24 Thread Michael Van Canneyt
On Tue, 24 Sep 2013, Mark Morgan Lloyd wrote: How does one convert from the numeric value returned by SocketError to the name of the error (specifically, to e.g. EsockEINVAL rather than EsysEINVAL, i.e. to be in line with the definition of functions like fpbind)? use the errors unit. (speci

[fpc-pascal] Socket error messages

2013-09-24 Thread Mark Morgan Lloyd
How does one convert from the numeric value returned by SocketError to the name of the error (specifically, to e.g. EsockEINVAL rather than EsysEINVAL, i.e. to be in line with the definition of functions like fpbind)? I notice that the example for fpconnect at http://lazarus-ccr.sourceforge.n