On Jun 13, 2008, at 3:31 AM, Peter Bex wrote:
On Fri, Jun 13, 2008 at 12:02:57PM +0200, felix winkelmann wrote:
On Fri, Jun 13, 2008 at 9:16 AM, Peter Bex <[EMAIL PROTECTED]>
wrote:
What makes "require" different from "require-library"?
"require" is a function, which only executes at run-time. "require-
library"
would be a special form and expand differently, depending on whether
we perform static linking or dynamic linking (and such would expand
into
"(declare (uses ...))" or "require").
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.
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
