> 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. For example, I was able to reproduce the missing line 20 bug, and that was fixed with Peter's patch. I played a few games of WUMPUS tonight on my MSVC-compiled parrot, but haven't seen anything out of the ordinary. It works flawlessly, and is really cool to see something like that working on Parrot. The only things I could complain about would be case-sensitivity in commands (it's annoying to keep the capslock key and get screwed up when switching to other applications :), and the one or two seconds it takes to generate the maze and set itself up. Do you have any test cases for reproducing the two bugs you just mentioned in this thread? Thanks, Mike Lambert
