[Usocket-devel] use of unexported symbols in backend/openmcl.lisp

Chun Tian (binghe) binghe.lisp at gmail.com
Wed Dec 17 12:25:52 UTC 2014


OK, now I understand what’s done in CCL trunk (1.11), it starts to support IPv6, those removed symbols were IPv4 only.

Il giorno 16/dic/2014, alle ore 19:33, R. Matthew Emerson <rme at clozure.com> ha scritto:

> I notice that backend/openmcl.lisp uses many symbols that are internal to the ccl package.  In some cases, even exported symbols (such as ccl:%null-ptr) are referenced using the ccl:: notation.
> 
> This is bad practice, of course.  It also causes usocket to be semi-broken on the development version of CCL: socket-connect uses the unexported symbols ccl::host-as-inet-host, ccl::port-as-inet-port, and ccl::inet-connect.  These are no longer present.
> 
> I could probably add them back for the sake of compatibility, but I would prefer not to have to do this.
> 
> If there is functionality that usocket requires that is not available from a supported interface, I'd like to hear about it.  The best way to do that would be to write tickets at http://trac.clozure.com/ccl.
> 
> 
> 
> _______________________________________________
> Usocket-devel mailing list
> Usocket-devel at common-lisp.net
> http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/usocket-devel





More information about the usocket-devel mailing list