Carl Karsten wrote: > 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?
No, we don't want to avoid throwing errors when something is wrong, because then we won't know what's wrong until it is too late. However, in this case, we are relying on something that only got introduced in wxPython 2.8, and it's too early to require wxPython 2.8 for Dabo. -- pkm ~ http://paulmcnett.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/dabo-dev/[EMAIL PROTECTED]
