>From my point of view - it isn't.
As I said in an earlier post, my Befunge interpreter is broken. It was doing
well not so long ago. Anyway, since I wanted to add intlists and push/pop, I
made some modifications. But I can't test them, since Parrot seems to be
badly broken...
At first, I thought maybe I made some mistakes. But then I added some traces
here and there, and I ended up with:
....
print "before ["
print S0
print "]\n"
eq S0, "<", FLOW_GO_WEST
print "after ["
print S0
print "]\n"
....
The initial code was the line with the "eq" op.
Then I ran it, and got (amongst other traces):
....
(9,8) - '<' (ord=60) dir=2 stack=
before [<]
after [<]
....
That is, the branch does not seem to happen!
But it's even weirder than that... The first instruction of my test is indeed
a < instruction (go west), and the interpreter then behaves correctly!
And while I'm talking about strange things... Due to the fact that Parrot
does not branch to the correct label, I have an infinite loop (of course,
since the program flow does not follow the wanted path). Sometimes Parrot
loops infinitely, and sometimes it crashes with a segfault. I must say that I
don't push elements during the infinite loop, it is an infinite loop of
no-ops.
FYI, I just rsync'ed this afternoon (12/10/2002 14:52 GMT) my Parrot, and did
the traditionnal: perl Configure.pl ; make; make test
and yes, all the tests went ok...
So, when I ask "Is Parrot in a stable state?", it's in fact not a question -
I have my answer, and it's definitely a "NO" answer.
I don't know where the problem lies. And I really think it's Parrot, since my
interpreter was broken when I rsync'ed my version of Parrot, although it was
performing well before. Before here means sthg about two or three weeks (I
know it's quite a long time), since I haven't looked at Parrot since.
If someone wants to investigate the problem but is afraid of Befunge (one
could wonder why Befunge would scare someone :-) ), just ask...
Jerome, in a very perplexed mind
--
[EMAIL PROTECTED]
