On 04/10/23 08:25 -0700, Stepan Roh wrote: > While playing with Parrot I found a few bugs and problems in Befunge > interpreter. Although it is not important part of Parrot
What? Not important? I was one of the first small languages implemented! And saying that befunge is not important is like saying cows can't fly... Erm... Maybe I just mixed up things... Anyway... You get my point! :o) > - Befunge-97 directives (lines starting with =) are ignored Uh? I've never seen this in the specs... Do you have a pointer? In the following url: http://dufflebunk.iwarp.com/JSFunge/spec98.html, there is no such mention of this behavior. Anyway, I'm not going to commit this change, since the interpreter shipped with Parrot is Befunge-93 compliant, and not 97 (nor 98). ==> rejected. > - stdout buffering is disabled > - fixed bug in integer input (instead of read integer, length of it's > string representation was returned) > - fixed bug in integer input (only integers with one digit were > allowed which was fixed by using readline instead of read) Regarding all the i/o stuff, I know it was b0rken, but don't forget I wrote it in the early parrot days. I'm glad you've fixed it, but maybe things will change with Parrot i/o? ==> applied. > - when outputing integer, output one space as well to conform with specs D'oh! I've missed it?! Thank you. ==> applied. > I tested all Befunge scripts I have and there is one which does not work > as expected. I attached it as pascserp.bef, it is also mentioned in > README. > > Hope I did everything right. Just missed the MANIFEST (pascserp.bef) and the changelog, fixed. You make me guilty, since I *know* I should go through befunge's TODO list... Anyway, I think the better would be to restart from scratch in imcc instead of pasm... Thank you, Jerome -- [EMAIL PROTECTED]
