ESL Master Include File
How about this ... the booleans 'true' and 'false' in 'types.e' are the
kind of thing that almost all ESL modules might need and I'm pretty sure
there will be other 'universal features' as well, as we go along.
I would propose a 'master' include file for all esl modules, which would
make it easier for all coders to work within some common infrastructure.
This would also make it possible to have global constants and types that
are associated generally with the ESL, such as ESL_VERSION_NUMBER and
ESL_VERSION_DATE and later, even things related to documentation and error
handling that might also need to be common to all ESL modules.
Even if, for example, we decided at some point to introduce a
sophisticated error handling system, this could still be coded as a
separate module 'error.e' but 'included' in 'esl.e'. This would cut
down on the number of modules that coders would have to remember to
include for the basic features of the ESL that will be common to almost
all modules.
Gordon
|
Not Categorized, Please Help
|
|
