Mail Index
This page is part of the web mail archives of SRFI 83 from before July 7th, 2015. The new archives for SRFI 83 contain all messages, not just those from before July 7th, 2015.
- syntactic tower?
- finally! minor naming suggestion
- put library <body> at top-level
- Re: syntactic tower?
- Re: put library <body> at top-level
- Re: put library <body> at top-level
- Re: put library <body> at top-level
- Re: put library <body> at top-level
- Re: put library <body> at top-level
- Re: put library <body> at top-level
- Re: put library <body> at top-level
- Re: put library <body> at top-level
- Overuse of strings
- Re: put library <body> at top-level
- Re: put library <body> at top-level
- Re: put library <body> at top-level
- Re: put library <body> at top-level
- Re: put library <body> at top-level
- Questions, loose ends, misprints, etc.
- Re: syntactic tower?
- Re: Questions, loose ends, misprints, etc.
- indirect-export in macro
- Re: Questions, loose ends, misprints, etc.
- Re: indirect-export in macro
- Re: indirect-export in macro
- Re: indirect-export in macro
- Re: Questions, loose ends, misprints, etc.
- Re: Questions, loose ends, misprints, etc.
- Re: indirect-export in macro
- Re: indirect-export in macro
- Re: Questions, loose ends, misprints, etc.
- Re: Questions, loose ends, misprints, etc.
- Re: Questions, loose ends, misprints, etc.
- Re: Questions, loose ends, misprints, etc.
- Re: Questions, loose ends, misprints, etc.
- Re: Questions, loose ends, misprints, etc.
- Re: Questions, loose ends, misprints, etc.
- Re: put library <body> at top-level
- Re: put library <body> at top-level
- import suggestion
- Re: import suggestion
- Re: put library <body> at top-level
- import/export asymmetry
- Re: put library <body> at top-level
- Re: Questions, loose ends, misprints, etc.
- Re: import/export asymmetry
- wrapping procedures
- fundamental design issues (long message)
- Re: fundamental design issues (long message)
- Re: fundamental design issues
- Re: wrapping procedures
- Re: fundamental design issues (long message)
- Re: Questions, loose ends, misprints, etc.
- Re: wrapping procedures
- Independent optimizing compilation [was: fundamental design issues]
- Library semantics correction
- Re: wrapping procedures
- Re: fundamental design issues (long message)
- Re: Independent optimizing compilation [was: fundamental design issues]
- Re: fundamental design issues (long message) [files]
- Re: fundamental design issues (long message)
- Re: Questions, loose ends, misprints, etc.
- Re: import/export asymmetry
- Re: Independent optimizing compilation
- Re: Library semantics - higher level imports
- Re: Library semantics - higher level imports
- Re: import/export asymmetry
- Re: Independent optimizing compilation
- Re: Independent optimizing compilation
- Re: Independent optimizing compilation
- Re: Independent optimizing compilation
- library representation (was Re: fundamental design issues)
- Re: Independent optimizing compilation
- Re: library representation (was Re: fundamental design issues)
- Re: Independent optimizing compilation
- Re: Independent optimizing compilation
- From: Sam Tobin-Hochstadt
- A portable implementation
- Re: fundamental design issues (long message)
- Re: fundamental design issues (long message)
- Re: fundamental design issues (long message)
- Reference implementation available?
- Re: Independent optimizing compilation
- Re: Independent optimizing compilation
- Re: Independent optimizing compilation
- Re: Independent optimizing compilation
- Re: Independent optimizing compilation
- Re: Independent optimizing compilation
- Re: Independent optimizing compilation
- Reified modules, module = environment?
- Re: Reified modules, module = environment?
- single vs. multi-sexp modules
- languages
- Re: single vs. multi-sexp modules
- Re: single vs. multi-sexp modules
- Re: single vs. multi-sexp modules
- Re: fundamental design issues (long message)
- Re: single vs. multi-sexp modules
- Re: single vs. multi-sexp modules
- Re: single vs. multi-sexp modules
- Re: single vs. multi-sexp modules
- Re: single vs. multi-sexp modules
- Re: Overuse of strings
- Re: Overuse of strings
- Re: Overuse of strings
- Re: Overuse of strings
- Re: Overuse of strings
- Re: Overuse of strings
- Re: Overuse of strings
- Re: Overuse of strings
- Re: Overuse of strings
- Re: Overuse of strings
- Re: Overuse of strings
- Re: Overuse of strings
- Re: Overuse of strings
- Re: Overuse of strings
- Re: Overuse of strings
- Re: Overuse of strings
- Re: Overuse of strings
- Draft extension of SRFI 83
- languages
- Re: languages
- Re: languages
- languages
- Re: languages
- Re: languages
- Re: languages
- Re: languages
- Re: languages
- Re: languages
- Reserved module name?
- From: Jonathan S. Shapiro
- Re: Reserved module name?
- Re: Reserved module name?
- From: Jonathan S. Shapiro
Mail converted by MHonArc