On Jun 13, 2008, at 1:25 PM, Peter Bex wrote:
On Fri, Jun 13, 2008 at 01:18:10PM -0700, Kon Lovett wrote:
What's the use of the distinction?
Not sure if it makes a lot of sense, but how about letting 'require'
do
this always, removing require-library? The functionality of the old
'require' could then be a hidden procedure local to the definition.
'require' is useful since it handles the package search.
From what I understood of Felix's description, so does require-
library.
Yes, but 'require-library', like 'require-extension', doesn't evaluate
its' arguments. Also, not sure what 'require-library', when not at the
top-level, means - especially if static linkage is used. Whereas
'require' is suitable for runtime, regardless of linkage mode.
Cheers,
Peter
--
http://sjamaan.ath.cx
--
"The process of preparing programs for a digital computer
is especially attractive, not only because it can be economically
and scientifically rewarding, but also because it can be an aesthetic
experience much like composing poetry or music."
-- Donald Knuth
_______________________________________________
Chicken-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/chicken-users
Best Wishes,
Kon
_______________________________________________
Chicken-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/chicken-users
