Hi
I'm not so sure that you would have hurt anyone's feelings too much by
terming the behaviour's bloat ware. The reality is that most behaviours
shipped with director need to almost every possible use of the behaviour.
That means when you go to write your own, you'll find significant amounts of
redundancy and code that means little to your particular situation. However,
they also tend to be more heavy in error correction code then most people
care to write, something that almost all of us fall prey to from time to
time when we have to write something too quickly. We don't get to go back
and do little error checks to say check if something is a list before we
perform a list operation.. we trust that our own programming prowness will
suffice not to mix data types etc.. newbies don't always realze the
difference between simple things like a text member or a field, so a quick
check of these is required for a prebuilt behaviour.
Just my thoughts..
Sincerely
Mark R. Jonkman
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
