>>12
I can see you're just too
ACADEMIC to admit Scheme's inferiority. Carry on.
neither Scheme or Common Lisp have functions, they have procedures.
Wat? Check your goddamn facts. In CL they're called functions, and they are most certainly first-class. You clearly don't understand what Lisp-1s and -2s are.
http://www.lispworks.com/documentation/HyperSpec/Body/t_fn.htm
This is SBCL 1.0.9, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>;.
SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses. See the CREDITS and COPYING files in the
distribution for more information.
; loading system definition from /home/paul/.sbcl/systems/metabang-bind.asd
; into #<PACKAGE "ASDF0">
; registering #<SYSTEM METABANG-BIND {AE34A69}> as METABANG-BIND
STYLE-WARNING: implicitly creating new generic function BIND-GENERATE-BINDINGS
* (lambda ())
#<FUNCTION (LAMBDA ()) {B10E29D}>
I know damn well what the spirit of Scheme is: to give its users little twinges of academic glee every time they write a recursive iterative
procedure by hand. I'm just telling OP about it.
Just out of interest; what is the standard way to use TCP/IP sockets in Common Lisp?
Well shit, just a minute ago you were telling me that the Scheme standard's lack of everything was a plus. Now lacking
anything is a minus? Yes, it would be nice to have BSD sockets in the spec. If I had a time machine, I'd go back and tell the guys who wrote it that if they'd just write them in, Berkeley would free them in just a couple years and it would pay off big.