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
i never officially closed the repo to commits, but for those of you
awaiting parrot's release, it's now complete. you may commit freely.
thanks for your patience.
~jerry
On behalf of the Parrot team, I'm proud to announce Parrot 0.4.8,
"Eponymous." Parrot (http://parrotcode.org) is a virtual machine aimed
at running all dynamic languages.
You may now grab Parrot 0.4.8 from the CPAN.
Parrot 0.4.8 News:
- Compilers:
+ HLLCompiler: added tracing options, modified
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
# New Ticket Created by Allison Randal
# Please include the string: [perl #41280]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41280 >
larry's most recent change to S05 (more)
looks like I'll need the ability to attach
Attached patch adds new syntax documentation to docs/imcc/syntax.pod and
fixes some typos there. It now also indicates where various flags are
explained.
Is the shorthand syntax for function calls ("($P0, a :slurpy) = foo(3, b
:flat)") clear, or can we better use examples there?
-- bgeron
Index:
