On Mon, Apr 15, 2002 at 01:05:41AM -0400, Mike Lambert wrote: > > As a follow-up, I found one bug. Rather odd it is. The symptom is loading > > a program, doing a LIST > > and seeing only part of the code. Dumping the > > string-which-contains-the-code you can see the entire program in it (unlike > > the earlier described bug). The problem was in here: > > Clint, in terms of getting things in Parrot fixed, I think it's better if > you can provide a way to generate the bug, no matter how complex the case > is. Non-simple test cases are better than no test cases at all, imo.
This is hugely important. A regression test suite is an invaluable comodity. Bug fixing should nearly always start with creating and submitting a new test for the test suite that triggers the bug. That's the best way to ensure the bug doesn't reappear N days, weeks, or months later (and cost some other poor developers hours or days of wasted time). Tim.
