Hi,
I am positive I did not subscribe to this. The first posting I have
received was the usocket-0.7.0 announcement; before that, I never
heard of the project.
According to your archives, there were some list postings in August:
https://mailman.common-lisp.net/pipermail/usocket-devel/2016-Augus
I have pushed a new cl-net-snmp release (snmp-6.1) which depends on
“usocket-server” now. I hope both usocket-0.7.0.1 and snmp-6.1 could catch up
with Quicklisp dist releases of this month.
> Il giorno 26/ott/2016, alle ore 17:28, Zach Beane ha scritto:
>
> I get an error in the USOCKET-TEST s
Sorry, all my faults... They’re exactly the two packages that should depend on
the new usocket-server system. And I should really export all symbols in the
main usocket package (even some of them are not defined).
I have uploaded usocket-0.7.0.1 to the usual publication URL [1] with all known
i
I get an error in the USOCKET-TEST system that "SOCKET-SERVER" is not in
the usocket package.
The SNMP-SERVER system also no longer builds.
http://report.quicklisp.org/2016-10-26/failure-report/snmp.html#snmp-server
http://report.quicklisp.org/2016-10-26/failure-report/usocket.html#usocket-test
> Il giorno 25/ott/2016, alle ore 23:22, Anton Vodonosov
> ha scritto:
>
> Congrats!
Thanks!
>
> 26.10.2016, 00:20, "Chun Tian (binghe)" :
>> Separated USOCKET and USOCKET-SERVER systems (only the server part depends
>> on Portable-threads)
>
> Does it mean some public function which were
Congrats!
26.10.2016, 00:20, "Chun Tian (binghe)" :
> Separated USOCKET and USOCKET-SERVER systems (only the server part depends on
> Portable-threads)
Does it mean some public function which were previously present in the USOCKET
system now are unavailable until you load USOCKE-SERVER?
