Ray Racine wrote: > If you were seeging something like this, its because you using a textual > port proc with a binary port. The error message could be a bit clearer.
In an attempt to give users time to adapt to the distinction between binary and textual ports, v0.95 allowed textual operations such as get-char on binary ports. That went away in v0.96. If Sven don't need to perform any binary operations on the port, I think he should obtain a new textual port from it using transcoded-port. Will _______________________________________________ Larceny-users mailing list Larceny-users@lists.ccs.neu.edu https://lists.ccs.neu.edu/bin/listinfo/larceny-users
