Opened 6 years ago

Closed 6 years ago

#190 closed defect (duplicate)

Clarify the language defining modules

Reported by: arcfide Owned by: alexshinn
Priority: major Milestone: Second Public Draft
Component: WG1 - Modules Keywords:


From Andre Van Tonder:

On Fri, 20 May 2011, Andy Wingo wrote:

On Fri 20 May 2011 04:19, "Aaron W. Hsu" <arcfide@…> writes:

Yes, this is equivalent. The location of imports has no effect on their
importing. The Body elements are concatenated together and evaluated in
the context of an environment defined by the sum total of the imports.

I did not see this language in the report. Suggestion: add it, or point
me to the language

Going even further, the module toplevel is almost not described in the
report at all. Can we redefine a previously defined identifier? Can
we shadow an import with a definition? What is the scope of a module
level macro definition? Can we intersperse definitions and expressions?
I'm sure I can think of more unanswered questions in the same vein.

Change History (1)

comment:1 Changed 6 years ago by alexshinn

  • Resolution set to duplicate
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.