[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUe-dev] Changing gDebug()
From: |
James Thompson |
Subject: |
[GNUe-dev] Changing gDebug() |
Date: |
Sat, 10 Sep 2005 20:04:51 -0500 |
User-agent: |
KMail/1.8 |
I was thinking about gDebug calls tonight (I'm sick like that :)
If we were to alter our gDebug() calls to *always* return a value of True.
Then in our code instead of doing
gDebug(15,"hi")
we do
assert gDebug(15,"hi")
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.
A quick test with a hacked forms show this works.
What do people think?
Take Care,
James
- [GNUe-dev] Changing gDebug(),
James Thompson <=