Re: :export vs. define-public

[Eric E Moore]

Tom Lord <address@hidden> writes:

> Those two approaches (:export vs. define-public) to public v. private
> module contours are isomorphic, so what's the big deal?

:export makes it considerably easier to port scheme code across
multiple implememntations, since the code to deal with the module
systems, which are regrettably non-standard, can be kept separate from
the R5RS code.  If scheme had an official module system, it might not
need :export.  'till guile has a good compiler, I'd like to see it
possible to port code easily.  (I suppose one could write a
define-public macro for schemes that lack one, but it's still nice to
have :export)

-- 
Eric E. Moore

pgpbAlFxjyKTN.pgp
Description: PGP signature