On 16 Aug 2006, at 22:40, Jonathan Vanasco wrote:
if there's an issue, big or small, i want to know where it is. if
i can fix it-- great. if i can't fix it, i can document what the
issue is, so maybe i can fix it when able to or when something
goes wrong, i know where to look.
Sounds like a totally sensible approach.
I was being slightly flippant with my RAM/CPU is cheep comment
(though for me personally it does have some mileage) and I'm not
saying that
code should be a hack, and of course it must be tested properly.
I applaud your skill and commitment to tracking this down, even if
only to document it.
Good luck :)
Leo
