Peter Schuller <peter.schuller-Xe4VFYsu7VRWk0Htik3J/[EMAIL PROTECTED]> writes:
> For example, take read-line. If I remember correctly SBCL's read-line
> will signal a simple-error on EOF (unless told to return some special
> value). This to me is unacceptable in the context of a unified
> networking library; any I/O errors should be signalled using
> conditions that fit properly into a logical hierarchy.
Not to nitpick, but SBCL signals a condition of type
COMMON-LISP:END-OF-FILE.
If you have a test-case where this does not happen, please please
report is as a bug on sbcl-devel or sbcl-help. Or even just in private
email.
> can be modified, but otherwise one would have to modify SBCL itself to
> get the wanted behavior. The problem becomes worse if this situation
...or send a bug-report. ;-)
Cheers,
-- Nikodemus Schemer: "Buddha is small, clean, and serious."
Lispnik: "Buddha is big, has hairy armpits, and laughs."
_______________________________________________
Gardeners mailing list
[email protected]
http://www.lispniks.com/mailman/listinfo/gardeners
