module(system) Identifier;
bearophile
bearophileHUGS at lycos.com
Sun Dec 14 05:26:03 PST 2008
Walter Bright:
> Doing it at the module level was deliberate. Not for technical reasons,
> but to make it easy for people doing quality code reviews. System
> modules should be segregated and given special attention. Having it
> dispersed throughout the code modules pretty much excludes being able to
> abstract it away properly.
Okay, that shots down my first idea.
But what about the second one? (That is to allow to specify a list of what to be safe of, at the top of the module?) A possible syntax:
module(safe1, safe2, ...) Identifier;
Bye,
bearophile
More information about the Digitalmars-d
mailing list