Re: define-library-alias Marc Nieper-Wißkirchen 26 Sep 2020 07:49 UTC

Am Sa., 26. Sept. 2020 um 03:05 Uhr schrieb Jim Rees <xxxxxx@gmail.com>:

> Whoa, hold the front door....

Please see my latest reply to John; in my initial example, I used the
wrong identifier for forging. Does this already clear the confusion I
have regrettably caused?

> Now a few things are starting to click based on our past conversations.    Your exported identifiers always include the full context from the library top-level -- yes?  Mine do not -- I only emit an a-list of name->label pairs for the exported identifiers, and then all of the label->binding mappings regardless of export.    Any literal syntax object (produced by syntax) that could be a variable value, or returned by a procedure or macro will contain the full context (at their point of evaluation), so macro output can contain references to non-exported identifiers.

Yes, this is not only true with your implementation but universally true. :)

Marc