Changes between Version 21 and Version 22 of Sysel

Timestamp:

2010-05-20T19:07:43Z (15 years ago)

Author:

Jiri Svoboda

Comment:

Nit.

Sysel

@@ -67 +67 @@
 Thus modules allow the source code to be broken into separate files and at the same time tie it together in a formal manner. When building a package or program, there is thus no need to specify all its source files informally in a makefile. It is sufficient to point the compiler to directories where it should look for source files and tell it which package we want built.
 
-Modules do not represent a namespace. Any symbols defined or imported in one module will be accessible (unqualified) in any other module within the same package. Names of global symbols in all modules of a package thus must be coordinated. Note that due to object-oriented nature of the language there are usually not very many global symbols defined per module.
+Modules do not represent a namespace. Any symbols defined or imported in one module will be accessible (unqualified) in any other module within the same package. Names of global symbols in all modules of a package thus must be coordinated. Note that due to object-oriented nature of the language there are usually not very many global symbols defined in a package.
 
 Definitions of classes can be split across multiple modules (but not packages). Thus large classes can be split accross multiple source files.