On Mon, 2007-11-19 at 17:38 -0600, Nathan Ingersoll wrote:
> On 11/19/07, The Rasterman Carsten Haitzler <[EMAIL PROTECTED]> wrote:
> > On Sat, 17 Nov 2007 11:11:55 -0600 "Nathan Ingersoll" <[EMAIL PROTECTED]>
> > babbled:
> >
> > personally i like defensive programming. it's better than every process
> > having
> > to trap its segv's/aborts and give u a debug trace and suddenly lose all
> > your
> > work/state. i think a compile or runtime definable "please btich to
> > stdout/err
> > about these problems" is the best way to go (all of evas and ecore are very
> > defensively programmed - set environment variables to turn on "bitch mode"
> > and
> > you can also enable "abort mode" for aborting on caught failures).
>
> Yep, I agree and EWL follows the same model. We have tons of parameter
> and type checks and they can be passed a command line flag (maybe an
> env variable too) to trigger an abort mode.
So can we combine the two, and get EWL to play nice with EVAS_DEBUG_SHOW
and EVAS_DEBUG_ABORT? Currently creating a single widget generates 20+
warnings... 95% are NULL warnings to be fair... but it's hard to see
what the other 5% are due to the number.
I'm willing to do some of the "if (obj != NULL) evas_object_show(obj);"
if people are happy for me to commit them.
Regards,
nash
[Venting on a little pet peeve he has with EWL]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
