Felix <fe...@call-with-current-continuation.org> writes: > From: Alaric Snell-Pym <ala...@snell-pym.org.uk> >> >> If there's macros involved, yes - but then autoloading >> macros makes no sense as they're loaded at compile time >> anyway. When you set up an autoload, no compile-time >> loading happens (no import library, etc) so the macros >> from the library aren't loaded - but at run time, if you >> call a procedure imported from the library, then the >> library is run-time-loaded. > > Sorry, I can't stop nagging: first, the constructed "<module>#<identifier>" > name will not work for identifiers that are imported from a different > module and then reexported, second: `global-ref' will be deprecated soon.
These are both easy enough to fix by just importing the module without requiring it, and arranging for the first call to do the require. The only problem with this is you'll get warnings about importing undefined identifiers. I don't suppose we could have a declaration or some way to suppress these warnings for individual identifiers and/or modules? -- Alex _______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
