tag:blogger.com,1999:blog-2772753380875006713.post6035413964086147908..comments2008-05-28T11:27:28.652-07:00Cokehttp://www.blogger.com/profile/01745512237217656642noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-2772753380875006713.post-64235104984320327702008-05-28T11:27:28.652-07:002008-05-28T11:27:28.652-07:00I can confirm what chrisdolan said with parrot-0.6.2<BR/>It also showed "> " by default, before I changed anything to squaak.pir<BR/><BR/>The culprit seems to be in compilers/pct/src/PCT/HLLCompiler.pir<BR/>(notice that the second occurence of PCT is uppercase, which apparently changed since you wrote this post)<BR/>line 502 reads: <BR/>code = stdin.'readline'('> ')<BR/><BR/>which probably would print a prompt in all interactive casesJoerihttp://www.blogger.com/profile/01422728563455858774noreply@blogger.comtag:blogger.com,1999:blog-2772753380875006713.post-28717161038764591832008-04-04T02:46:23.749-07:002008-04-04T02:46:23.749-07:00Chris,<BR/><BR/>that seems odd. What happens if you remove the line to set the prompt?<BR/>Did you check out a fresh parrot? Could you try that?<BR/><BR/>Someone sent a patch the the mailing list to make "> " a default prompt, but I don't think it was applied (and IMHO, it shouldn't).<BR/><BR/>You can also <A HREF="parrotcode@gmail.com" REL="nofollow">mail</A> me, if you need detailed help.kjshttp://www.blogger.com/profile/18109327874846144778noreply@blogger.comtag:blogger.com,1999:blog-2772753380875006713.post-48752282424980740852008-04-03T21:08:41.064-07:002008-04-03T21:08:41.064-07:00When I set<BR/><BR/>$P1.'commandline_prompt'('> ')<BR/><BR/>then Parrot prompts with "> > ". It seems that HLLCompiler prints a "> " after the prompt no matter what. Is this a bug, or did I misunderstand?ChrisDolanhttp://profile.typekey.com/ChrisDolan/noreply@blogger.comtag:blogger.com,1999:blog-2772753380875006713.post-58998099634940088592008-03-17T03:31:10.756-07:002008-03-17T03:31:10.756-07:00I'm a bit hesitant to write more on PIR, as there's already a lot of docs to be found on that. However, what I can do is to explain PIR a bit more inline with the rest of the tutorial (whenever we write PIR, which is not a lot).kjshttp://www.blogger.com/profile/18109327874846144778noreply@blogger.comtag:blogger.com,1999:blog-2772753380875006713.post-28992538868949012782008-03-16T22:45:32.675-07:002008-03-16T22:45:32.675-07:00Nice series so far, I'm really looking forward to seeing the rest. One issue though: I know we can go and look up PIR in the docs, but it'd be nice to have a quick overview here anyway, just a short explanation of what PIR is and the sorts of things you can do with it, from the point of view of code that you'd see in the output of a compiler or in language builtins.arcadyhttp://www.blogger.com/profile/06394805356595604336noreply@blogger.comtag:blogger.com,1999:blog-2772753380875006713.post-76636759184494338202008-03-15T07:42:04.469-07:002008-03-15T07:42:04.469-07:00this is really great!! I look forward to seeing more examples! I will join the fun soon I hope!Proclushttp://www.blogger.com/profile/07783409770187038602noreply@blogger.com