pack/unpack (was Re: rfc 2045 base64 encoding/decoding module)

[sen_ml at eccosys dot com]

thanks for the response!

val> My suggestion would be to separate reading/writing binary data and
val> forming the perl/python-like structures.
val> Namely, I would make a separate module

that sounds like a better idea than choosing one or the other.

[ some snippage ]

val> Of course, all these functions should read/write to/from ports.

val> Then, on the base of these functions, the perl-like and/or python-like 
val> struct modules could be written.

right.  so may be someone else can implement the higher-level
functionality ;-)  i hope to get around to doing the low-level routines
soon.

btw, looking through r5rs, i noticed in 7.6.1:

    (with-input-from-file string thunk)
    (with-input-to-file string thunk)

  String should be a string naming a file, and proc should be a procedure...

but i don't see any mention of 'proc' -- did the authors mean 'thunk'
here or am i misunderstanding something?  is there an errata list
around somewhere?