This is the mail archive of the
guile@sourceware.cygnus.com
mailing list for the Guile project.
Re: rfc 2045 base64 encoding/decoding module
neil> AFAIK, in the current module system, (define-public name ...) is
neil> the same as (define name ...) followed (or preceded, for that
neil> matter) by (export name).
thanks for the explanation!
on a separate note, i have a prototype native encode-base64 routine
now that seems to work in a few test cases (that is to say, i haven't
tried it out on enough to get it to fail yet). i'm currently working
on finishing up the decode-base64 routine.
the routines work on strings and i was wondering whether it might be
better for them to work on ports. does anyone have any opinions
regarding this matter?
once i'm done w/ that, i'm hoping to work on the pack/unpack thing.
i'm much more familiar w/ the perl version than the python one though
so what i make may end up more perlish than pythonish (at least at
first). i have the same question regarding whether the routines
should operate on ports as compared to strings. any opinions?