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.
Hi, R. Matthew Emerson
Thank you for letting us know this. Please feel free to make any change you want in new versions of CCL, I think it’s actually our (usocket) job to support CCL versions as many as possible. And I’ll check backend/openmcl.lisp in next days to see if it’s possible to use only exported symbols from CCL trunk. If there is functionality that we require but is not available as exported symbols, I’ll let you know, by submitting tickets.
Regards,
Chun Tian (binghe)
Il giorno 16/dic/2014, alle ore 19:33, R. Matthew Emerson rme@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@common-lisp.net http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/usocket-devel
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@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@common-lisp.net http://mailman.common-lisp.net/cgi-bin/mailman/listinfo/usocket-devel
-
Chun Tian (binghe) -
R. Matthew Emerson