[Larceny-users] current-{in, out}put-port assignable but not current-error-port

Derick Eddington derick.eddington at gmail.com
Fri Mar 20 03:56:10 EDT 2009


Is current-error-port intentionally not assignable?  I have code which
parameterizes all three current-*-port (and imports them via a
compatibility library because R6RS's are technically not directly
assignable (I think) (but they should be)).


Larceny v0.97a4 (alpha test) (Mar 18 2009 22:48:58, precise:Linux:unified)
larceny.heap, built on Wed Mar 18 22:50:40 PDT 2009
ERR5RS mode (no libraries have been imported)

> (import (rnrs io ports))
Autoloading (rnrs io ports)
Autoloading (larceny deprecated)
Autoloading (rnrs lists)

> (current-input-port (current-input-port))
#<INPUT PORT *console-input*>

> (current-output-port (current-output-port))
#<OUTPUT PORT *console-output*>

> (current-error-port (current-error-port))


Error: Wrong number of arguments to procedure #<PROCEDURE current-error-port>,
    which expected 0 but got 1
Entering debugger; type "?" for help.
debug> 





More information about the Larceny-users mailing list