Re: Changing gDebug()

Am Samstag, den 10.09.2005, 20:04 -0500 schrieb James Thompson:
> When optimization is requested (python -O) assert statements are left
> out of 
> the generated code.  So we would regain all the time lost to those
> function 
> calls.  We would also be able to put gDebug calls in places where
> we've 
> removed them in the past to increase performance.

I like this idea, as I was wondering about how to remove those
debug-steps for non-debug-runs to gain performance. But on question is
still left then. Where do we add that -O option ? Do we have to write
"gnue-forms -O -other-options ... myForm.gfd" every time ? Or the other
way round, if -O is included how can we add debug-output on a
"per-run-basis" ?

Have a nice day
Johannes

-- 
BYTEWISE Software GmbH               Tel +43 (5577) 89877-0
i.A. Johannes Vetter                 Fax +43 (5577) 89877-66
A-6890 Lustenau, Enga 2              http://www.bytewise.at
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Wir bieten Installation und Support für Ubuntu: ein auf
GNU/Linux basierendes Softwaresystem für Arbeitsplatzrechner

_______________________________________________
Gnue-dev mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnue-dev

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBDI/bbVTjHnzKwdk0RAmXFAJwNFg21anzVffME0NF+/qm/IXh8RQCgplMO
E86j0/E8QDbMcwdulymxV7Y=
=n9k1
-----END PGP SIGNATURE-----