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: Wed, 26 Sep 2007 16:11:12 +0900 (JST)
- From: Curt Sampson <cjs@example.com>
- Subject: Re: [tlug] Policy on debug codes
- References: <46E8EE01.4040404@cnt.mxt.nes.nec.co.jp> <Pine.NEB.4.64.0709141931330.4169@homeric.cynic.net> <46F9BA8B.3010507@simon-cozens.org> <46F9DE14.6000506@cnt.mxt.nes.nec.co.jp> <c4007cba0709252330t3097b1d7w7b9327b6203e9fd7@mail.gmail.com>
On Wed, 26 Sep 2007, Kim Ahlstr$Bv(Bm wrote:
Anyone tried Perl's Smart::Comments.... It's also recommended in Perl Best Practices[1], which I in my turn would recommend.
Actually, looking at this and understanding what people mean now, my "best practice" would actually be to remove debug code as soon as possible, on the basis that the more code you have cluttering up your code base, the harder it is to read and maintain.
cjs -- Curt Sampson <cjs@example.com> +81 90 7737 2974 Mobile sites and software consulting: http://www.starling-software.com-- To unsubscribe from this mailing list, please see the instructions at http://www.tlug.jp/list.html Please visit our sponsor at http://www.primustel.co.jp/tlug/
- References:
- [tlug] Policy on debug codes
- From: Nguyen Vu Hung ①
- Re: [tlug] Policy on debug codes
- From: Curt Sampson
- Re: [tlug] Policy on debug codes
- From: Simon Cozens
- Re: [tlug] Policy on debug codes
- From: Nguyen Vu Hung
- Re: [tlug] Policy on debug codes
- From: Kim Ahlström
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] Policy on debug codes
- Next by Date: [tlug] python socket.connect() issue
- 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