Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] Policy on debug codes
- Date: Fri, 14 Sep 2007 03:03:23 +0900
- From: "Stephen J. Turnbull" <stephen@example.com>
- Subject: Re: [tlug] Policy on debug codes
- References: <46E8EE01.4040404@cnt.mxt.nes.nec.co.jp> <46E90539.6060207@dcook.org> <46E90A22.7070209@cnt.mxt.nes.nec.co.jp> <46E90F58.5010607@dcook.org> <78d7dd350709130852r4ac5273bs86e37b2510642281@mail.gmail.com>
Nguyen Vu Hung writes: > After all bugs are fixed, of course TRACE() can be removed. Since you can't prove that all bugs are fixed, you can't remove TRACE() ever. :-) In Perl you can of course define TRACE() to be a do nothing function, and it should get optimized away (even Emacs Lisp does that). Your compile time will increase slightly, but if that matters you're doing something else wrong anyway -- it should always be possible to keep compile time down to a negligible fraction of total time in production use, and a 10% increase in negligible is still negligible.
- Follow-Ups:
- Re: [tlug] Policy on debug codes
- From: Nguyen Vu Hung
- References:
- [tlug] Policy on debug codes
- From: Nguyen Vu Hung ①
- Re: [tlug] Policy on debug codes
- From: Darren Cook
- Re: [tlug] Policy on debug codes
- From: Nguyen Vu Hung
- Re: [tlug] Policy on debug codes
- From: Darren Cook
- Re: [tlug] Policy on debug codes
- From: Nguyen Vu Hung
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] Policy on debug codes
- Next by Date: Re: [tlug] Fair use effects on the economy
- Previous by thread: Re: [tlug] Policy on debug codes
- Next by thread: Re: [tlug] Policy on debug codes
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links