On Feb 13, 2008, at 3:44 AM, IOhannes m zmoelnig wrote:
Hans-Christoph Steiner wrote:
I think this kind of thing should be caused by a real world
problem rather than a hypothetical.i think this discussion _is_ triggered by a real world problem, and
you seem to try making it hypothetical.
I guess I missed it then, where was it described? Here's how the
thread started:
"Currently pdlua loads all *.lua files, which complicates working
with *.lua modules not intended to be used as pd classes: Those would
have to be in a directory outside of Pd's search path to not pollute
Pd's namespace. "
So how about using Pd's normal tools for handling name clashes and
additionally, using a naming prefix like "lib" for the lua files that
are not intended to be Pd objectclasses (as I described earlier)?
Another possibility is using a subdir for these files.
Then we would not have to break the .lua naming convention and still
solve the problem easily. And people wouldn't have to learn a new
detail to get things working. They would then need good style once
they get things working, which I think is a preferrable to having to
learn naming conventions in order to get things working.
.hc
Man has survived hitherto because he was too ignorant to know how to
realize his wishes. Now that he can realize them, he must either
change them, or perish. -William Carlos Williams