Re: [racket-dev] processing the internal-context of a mod?

[Danny Yoo]

> I'm trying to understand the case analysis so that I can properly
> generate the code to construct the namespace.  The documentation says
> I have four things to keep track of for internal-context:
>
> case 1: #f: it's empty
> case 2: #t: it's all the requires
> case 3: stx: it's the lexical context of the wrapped syntax object
> case 4: (vectorof stx): ???
>
> Case 2 seems fairly straightforward to me: to construct the namespace
> for a module, I take all the symbols defined in its prefix, and
> combine that with all the exports of all the required modules.

Followup:

I have yet to synthesize a case other than case 2 or 3, so I have to
admit I still don't understand.

In my own experiments, if the internal context is a syntax object,
then it's an object whose datum is #f, and whose wraps consist only of
module-rename wraps.  Am I guaranteed that the syntax objects
associated to the module's internal context only consist of
module-rename wraps?
_
  Racket Developers list:
  http://lists.racket-lang.org/dev

Re: [racket-dev] [plt] Push #26710: master branch updated

[Asumu Takikawa]

On 2013-04-25 14:55:45 -0400, as...@racket-lang.org wrote:
> a15fa5b Asumu Takikawa  2013-04-20 23:18
> :
> | Start on a notation section for the Reference
> :

This is in response to the "How to read procedure documentation?" thread
from the users list. It documents how to read some of the blue boxes
with contracts from the Reference.

I'm not sure this is the best place to put it, so feedback appreciated
on where it should go (or anything else).

Ryan was also suggesting that there should be explanations of blue boxes
interspersed in the Guide as well (in 2.2.4 for example) with more
Guide-like language, which I agree would be a good thing to add.

Cheers,
Asumu
_
  Racket Developers list:
  http://lists.racket-lang.org/dev