Hi. I get the following error when I try to parrot -o basic.pbc merged_basic.pasm (in parrot 0.0.10 on Win32):
(error) line 164: parse error, unexpected INTC, expecting '\n' The error appears to be in line 164 of stackops.pasm, which seems to be missing a comma. I looked at CVSweb and it seems the line is still missing a comma. Line 171 is also missing a comma. Also line 280 of expr.pasm. I also got an error from the "puts" function on line 120 of alpha.pasm. I don't know what puts means, but changing it to "print" allows that to compile. The bad news is that when I then try to parrot it, Windows throws me an error window saying parrot died. I don't know why. When I comment out all of the .includes from merged_basic.pasm except for basicvar.pasm and expr.pasm, pipe -d7 into a file, I get a thousand lines describing command, and then it just dies with no error message after a substr (on line 1182, I believe - annoying that -d doesn't print out line numbers or labels or anything). Interestingly, if I deleted the last 109 lines from the file including that substr, then the program dies again. This time it dies in merged_basic.pasm a few lines in. In fact, when I uncomment another .inculde, I again get a crash after printing (almost!) exactly 1000 lines (i.e. 1000 commands). On the other hand, if I uncomment all of the .includes, then I get a 2374-line file, but still get the crash. Oh silly me, the lines are cutoff in the middle. Windows must be buffering its output. (If I don't .include expr.pasm, the compile finishes.) I have to imagine that this thing has compiled before. Any ideas? Is it a Windows-specific issue? -Amir __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com
