Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
It's been many months since I submitted my original version of sendto
for sb-bsd-sockets, and let's face it, it's not going to get better
any time soon.
I know I was suggested to clean the code a bit before it would be
committed, but I still resubmit the exact same code, with the
* it still works better and faster and is cleaner than the code
currently in CVS or (IMNSHO) other versions submitted here.
* it's not only less work for me and/or my colleagues to maintain it,
it's also less work for these people who keep writing their own
versions of sendto (e.g. Scott Bell, recently)
* it's a good basis for anyone (=3Dnot just me) to make things cleaner,
for instance, the next person who'd otherwise have to write his own
version of sendto.
The issues were:
* my introducing a generic "iobuffer" abstraction, which is similar in
spirit to the CFFI shareable-vector abstraction, but not publishing my
abstraction in a nice place, only using it internally for packet I/O.
* my not doing the Right Thing (whatever that is) for character
encoding, assuming ascii or latin1 (just like the existing packet code
I believe these issues are minor, and that ugly code that works in
usual cases is better than beautiful code that doesn't exist yet.
(This is the TUNES guy speaking!)
Could the attached patch be included in SBCL? [Test program also attached]
[ Fran=E7ois-Ren=E9 =D0VB Rideau | Reflection&Cybernethics | http://fare.tu=
When everything seems to be going against you, remember that the airplane t=
off against the wind, not with it. -- Henry Ford