That's why you comment your code. Take the extra time and put a bit of effort into explaining yourself. Add in a paragraph explaining what's going on, link to whatever solution you found on the web (who knows it might still exist), and just outright bloat it with comments. You might find it annoying now, but I can't tell you how many times I've thanked myself for doing stuff like this when I've revisited old code. You don't need to comment every line, but put a nice hearty paragraph at the beginning of the confusing part and things should be nice and clear to anyone who has to maintain it. "Daniel Kasak" <dkasak@xxxxxxxxxxxxxxxxxxxx> wrote in message news:1180577761.31799.21.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx > On Wed, 2007-05-30 at 13:40 -0500, Richard Lynch wrote: > ..snip... >> If I returned to this 2 years later ( or > God forbid, someone else had to look at it ), they wouldn't have a clue > what it was doing, or why. > ..snip .. > Daniel Kasak > IT Developer > NUS Consulting Group > Level 5, 77 Pacific Highway > North Sydney, NSW, Australia 2060 > T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 > email: dkasak@xxxxxxxxxxxxxxxxxxxx > website: http://www.nusconsulting.com.au -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
