From: Phil Mobley <phil at mobleybros dot com>
I have the same design issue:
A) Operator_convert allows for intuitive code.
B) Operator_convert means that the user may now write slower code than
ever before, without realising it.
The problem for me is that the user will think "why is this ElfData
plugin running so slow", when in fact all they need to do to make it N
times faster (anything from 1 to 1 trillion) is declare their datatype
as ElfData, instead of string :o(
I'd rather have some kind of operator_convert feature where you must
explicitly choose a global "unlock" method to unlock operator_converts
without getting an error message. Like this:
ElfDataPlugin.IAmAwareThatOperatorConvertsCanBeMisusedAndIKnowWhatIAmDoi
ngWhenIUseThemSoPleaseDisableTheWarningMessageThankYou
Or somehing like that.
Maybe I'll just let the users write slow code when just spending a few
seconds to fix it by changing string to ElfData (in just the few key
points), would suffice. Bah.
--
Theodore H. Smith - Software Developer - www.elfdata.com/plugin/
Industrial strength string processing code, made easy.
(If you believe that's an oxymoron, see for yourself.)
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|