diff options
| author | Andy Wingo <wingo@pobox.com> | 2010-06-01 22:02:06 +0200 |
|---|---|---|
| committer | Andy Wingo <wingo@pobox.com> | 2010-06-02 22:19:40 +0200 |
| commit | bcec8c36996467433a17680e5a2ef27da2baecc5 (patch) | |
| tree | 098e282d345dcf68c5d8bcc0b829470ad84bd9e9 | |
| parent | c08adae4602e8aa2ac7d1d174292953f5a1ff2a7 (diff) | |
| download | guile-bcec8c36996467433a17680e5a2ef27da2baecc5.tar.gz | |
minor NEWS tweaks
* NEWS: Fix wordings.
| -rw-r--r-- | NEWS | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -132,7 +132,7 @@ module where the `library' macro is defined, not in the new module. `define-module', `use-modules', `export', and other such macros have been rewritten as hygienic macros. This allows the necessary referential -transparency for the R6RS `library' for to do the right thing. +transparency for the R6RS `library' form to do the right thing. ** Compiler and VM documentation updated @@ -164,8 +164,8 @@ out! It was a little-known implementation detail of Guile's module system that it was built on a single hierarchical namespace of values -- that -if there was a module named `(foo bar)', then there was a also module -named `(foo)' with a binding from `bar' to the `(foo bar)' module. +if there was a module named `(foo bar)', then in the module named +`(foo)' there was a binding from `bar' to the `(foo bar)' module. This was a neat trick, but presented a number of problems. One problem was that the bindings in a module were not apparent from the module |