1 Nov 2006 19:06
Re: ecl_stream_to_handle bug? (Was: Latest changes)
2006/11/1, Dave Roberts <dave@...>: > Juan Jose Garcia-Ripoll wrote: > > Well, the thing is that this routine does not know how to deal with > > sockets and sllime does communicate via sockets with ECL. > > I'm not sure exactly how Slime does its thing, but sockets still have > file handles, no? That is, at least under Unix-like systems, I would not > expect this routine to return -1 unless the particular stream was closed. SB-SOCKETS in ECL are implemented as CLOS objects. The routine you try to use does not know about these objects. Indeed, this routine was not at all expected to be exported. It is so level it was thought for internal use in the core library. I made it public because I was asked to do so. Now it does not fit your work, well, extend it!In your case you probably do not even need do it. Your function must check first whether the input/output stream is a CLOS object and return NIL in that case because isatty() does not make a sense on Gray streams. Juanjo ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
In your case you probably do not even need do it. Your function must
check first whether the input/output stream is a CLOS object and
return NIL in that case because isatty() does not make a sense on Gray
streams.
Juanjo
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
RSS Feed