One of the things that I didn't like about the VFE framework was code that would
avoid an error like this:
IF <this will work>
<do this>
ENDIF
Which often made debugging a problem much harder because I would get an error
when something in a much different block of code relied on <do this> happening
and then I would have to work backward trying to figure out why thing's weren't
setup as I was expecting.
So now I see:
> Revert back to revision 3088 until Ed can post a fix that only loads AUI
> if it's available and/or if it is actually being used.
"only loads AUI if it's available" sounds vary similar to my VFE gripe. I think
I have seen some other "defensive coding" as I browse the dabo code, but I don't
understand everything enough to know how similar it is.
So, do we really want the dabo framework to actively avoid throwing errors when
something is wrong?
Carl K
©2007 Carl Karsten |
