On Tuesday 16 January 2007 16:56, Isaac Freeman wrote:
\
> So, for my purposes I need an embedding interface that allows for more
> control of the interpretter, e.g. the ability to inspect/modify
> namespace(s) and eventually control which opcodes are allowed, or
> register callbacks for opcodes (i
So, for my purposes I need an embedding interface that allows for more
control of the interpretter, e.g. the ability to inspect/modify
namespace(s) and eventually control which opcodes are allowed, or
register callbacks for opcodes (i.e. file access, etc) for security
purposes.
Tackling the first
Hi,
I would like to add Parrot as a scripting engine for a software project.
Embedding it is no problem, but I was wondering if the current
implementation supports the embedder to provide functions to the Parrot
bytecode applications? The idea is that I would like to access C
functions the embedde
On Thu, 13 Feb 2003 10:36:43 +0100, Alin Iacob wrote:
> On February 13, 2003 2:00 chromatic wrote:
>>I'm experimenting with embedding Parrot at the moment, and have a few
> questions.
> Some time ago Brent Dax propossed the following PDD:
> http:[EMAIL PROTECTED]/msg11922.html
Thanks, that answe
On February 13, 2003 2:00 chromatic wrote:
>I'm experimenting with embedding Parrot at the moment, and have a few
questions.
>
>1) How do I get data into Parrot-space? I can pass arguments to
>Parrot_runcode() or I could populate some registers directly, but both
>approaches have their drawbacks.
I'm experimenting with embedding Parrot at the moment, and have a few questions.
1) How do I get data into Parrot-space? I can pass arguments to
Parrot_runcode() or I could populate some registers directly, but both
approaches have their drawbacks. I could probably create PMCs directly, but
that
