On Sep 27, 2006, at 12:23 PM, Vince Teachout wrote:
Contrast that with VFP, where everything is in the same
namespace. When was the last time you used @SAY/GET code? How
about all those DDE* commands? Or all the Macintosh-specific
commands? Wouldn't it make more sense to factor that stuff out
into separate modules, and only use them when they are needed?
Instead, you have all that junk floating around in the core of the
language.
The only drawback with that is sometimes you want to use Library X,
and when you try to use it, you find X needs C, and C needs A.
But I'm talking from a very limited exposure here, and that doesn't
seem to come up often as a topic of discussion, so I assume that
it's not really a major issue.
Modules are usually self-contained; those that require other modules
will tell you up front. For example, I record my screencasts using
pyvnc2swf, and that requires an imaging library. If I were to try to
run it without the dependency, I get a message telling me about that,
and where to get the required package. Same thing would happen if you
use Dabo and try to run a report: Dabo requires ReportLab to do
reports, and you'll get an informative message about where to get
ReportLab.
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
