Hi,
Freysteinn Alfredsson <freysteinn@xxxxxxxxx> writes:
[snip]
> Basically I would like to see a more structured approach to manage
> modules. Were modules are categorized in "modes", "libraries" and
> "standard libraries". Making them easily distinguished.
This subject has been argued to death before, I recall some
interesting points coming from bpalmer on #xemacs last summer I think.
You should keep an eye out for the object oriented feature draft I
asked hrop to come up with. Maybe he'll include some sort of
namespace mechanism too.
Few points I recall:
* I had the idea to use :: as a namespace separator. This might work
okay since it's rather rare to use :: in symbol names.
* Brian (bpalmer) wanted some sort of conditional export mechanism for
the namespaces too - aka perl - I think. I'm not entirely sure how
I feel about it. Should we include a mechanism to export names to
the global namespace (providing we actually do namespaces)?
Probably, if not the global namespace, then something quite similar
for each file. Should we allow the programmer to select which names
get exported and which names need explicit reference? And what
effects does that selection mechanism have on tab completion?
That's it for now. I know I'm quite vague, but I'm waiting for hrop
to post his syntactical sugar draft and then we can discuss that and
the implementation issues.
I'm also slightly pissed at the lack of documentation for exceptions.
That's maybe a related issue, but does stand on its own. At least I'd
like C-h E (or something) to describe exceptions, some time in the
future.
Johann
--
This line is left blank intentionally
|