On Wed, 29 Nov 2000, Dan Sugalski wrote: > At 09:51 AM 11/29/00 -0800, Dave Storrs wrote: > >I have a feeling this is a stupid question, but I have to ask anyway. > > > >Do we really need to pass in a PerlInterp pointer? Or can perl6_parse > >just create one for itself if/when it needs one? If created, it could of > >course be kept around so that it didn't need to be re-created later. > > Yup, we do. We'd call this (or something like it) when doing the whole > eval/do/require/use thing, so we may well be parsing into an existing > interpreter. Sorry, I guess I didn't phrase that well...I realize we're going to *need* an interpreter. My question is, does it have to be created outside of the perl6_parse(...) function? I just thought that if we could eliminate one more parameter, one more "magic cookie" that the caller (in an embedded situation) needs to work with, that would be a good thing. Dave
- Re: The external interface for ... Chaim Frenkel
- Re: The external interface for the ... Nick Ing-Simmons
- Re: The external interface for the ... Nick Ing-Simmons
- Re: The external interface for ... Tim Bunce
- Re: The external interface for the parser piece Chaim Frenkel
- Re: The external interface for the parser piece Dan Sugalski
- Re: The external interface for the parser piece Steve Fink
- Re: The external interface for the parser piece Bryan C. Warnock
- Re: The external interface for the parser piece Dave Storrs
- Re: The external interface for the parser piece Dan Sugalski
- Re: The external interface for the parser piece Dave Storrs
- Re: The external interface for the parser pi... Dan Sugalski
- Re: The external interface for the parser piece Simon Cozens
- Re: The external interface for the parser piece Damien Neil
- Re: The external interface for the parser piece Nicholas Clark
- Re: The external interface for the parser piece Dan Sugalski