A vision for Parrot

Slaven Rezic wrote:

Benjamin Goldberg goldbb2@earthlink.net writes:

Walter Roberson wrote:

[…]

Speaking of layers: I take it that some thought has been put into
how to do operating-system escapes? So that one can (for example)
handle graphics? Or even just sockets? Seeing as some of the most
popular interpreted languages are by no means restricted to
text-only and have networking capabilities?

Remember, the parrot interpreter is written in C… it has to be.
Obviously, one would have parrot opcodes which result in calls to C
functions, which perform socket operations or graphics or whatever.

I dont’t think it will be opcodes, but rather a combination of loadlib
(load a DLL) and dlfunc (create a parrot-callable subroutine from a
DLL function). See core.ops.

Ok, so loadlib is one op, and dlfunc is another op :slight_smile:

···


my $n = 2; print +(split //, ‘e,4c3H r ktulrnsJ2tPaeh’
…“\n1oa! er”)[map $n = ($n * 24 + 30) % 31, (42) x 26]