At 05:08 PM 12/3/2001 -0500, Gregor N. Purdy wrote: >Hao -- > > > Perhaps premature/immature question: How do I access command-line > > arguments in Parrot? Should I try to create a new op or new ops? > >Last I knew, Dan wasn't ready for this. I committed some get/set ops >for the environment when the file open/close/read/write stuff went in, >but he removed them. I think he wants to acommplish get/set env (and >argc/argv access, I presume, too) some other way. > >Maybe they'll come via PMCs, I don't know.
I'm thinking argc/argv will come in via an array, probably just a global ARGS and that'll be it. I'm not sure it's worth much special-casing. Of course, that begs the question of how we set a variable in an interpreter that's not us, but that's a separate issue. Dan --------------------------------------"it's like this"------------------- Dan Sugalski even samurai [EMAIL PROTECTED] have teddy bears and even teddy bears get drunk