|
![](/i/fill.gif) |
Warp wrote:
> 1) It makes it clear where the names are coming from (which is especially
> important if you are using names from several different namespaces, as eg.
Actually, here's another great example.
I'm trying to figure out how to use a library based on sample code that
calls it. Both library and sample code suck (can you say 800-line macros? An
entire multimedia jukebox written in one 14000-line main()?)
But at least if the library names were in a namespace, I could distinguish
while I'm reading whether "audio_info" and "instance_modifier" and crap like
that was part of the library or part of the sample program, and drill down
until I found the actual types used by the library.
--
Darren New, San Diego CA, USA (PST)
Eiffel - The language that lets you specify exactly
that the code does what you think it does, even if
it doesn't do what you wanted.
Post a reply to this message
|
![](/i/fill.gif) |