Search the Forum for answers or post your questions to the
Quantum Leaps community
 |
 |
|
| Home | | | Products | | | Services | | | Downloads | | | Licensing | | | Developer Zone | | | Resources |
 |
| Overview | | | Discussion | | | Cookbook | | | Design Patterns | | | Bugs | | | Contributions | | | Credits |
Quantum Leaps Discussion Forum
Search the Forum for answers or post your questions to the |
||
| Return to Website | ||
 First |
 Prev |
 Reply |
 Forum |
Next  |
Last  |
| Viewing Page 1 of 1 (Total Posts: 2) |
| Author | Comment |
G. Guenzati
Jul 17, 07 - 4:40 AM |
Using Q_ASSERT
When some of the Q_ASSERT of the framework fires, I think it would be a great help to know the signal that has fired the ASSERT. Every more information regarding the moment in which the ASSERT fired is very important expecially when the problem happens in the field. Best regards |
Miro Samek
 Jul 23rd, 2007 - 6:18 PM |
Re: Using Q_ASSERT
I understand that any additional information about the bug is invaluable. But I really don't know how to make all this information available to the assertion handler. I believe that the strength of assertions derives really from their simplicity. So, I'm really reluctant to introduce any more complexity and burden on the application programmer in using assertions. Miro |
| First |
Prev |
Reply |
Forum |
Next |
Last |
bravenet.com| Privacy Statement | About Us | Contact Us | © 2004-2005 quantum Leaps. All rights reserved. |