Re^3: What is the big deal about PAR(rot)?


"be consistent"
	PerlMonks

Re^3: What is the big deal about PAR(rot)?

by kelan (Deacon)

on Mar 17, 2003 at 15:31 UTC ( [id://243660]=note: print w/replies, xml )

Need Help??

in reply to Re: •Re: What is the big deal about PAR(rot)?
in thread What is the big deal about PAR?

Parrot will produce bytecode, which is really an intermediary form. It will not be directly executable, you will still need an installed version of the Parrot VM to execute it, much like you need a Java VM to execute Java bytecode. This is not to say that something with functionality like PAR will not emerge, but from what I've read so far, it doesn't look like Parrot will include that functionality itself.

kelan

Perl6 Grammar Student

Comment on Re^3: What is the big deal about PAR(rot)?

Replies are listed 'Best First'.

Re: Re^3: What is the big deal about PAR(rot)?
by Elian (Parson) on Mar 17, 2003 at 15:36 UTC

End deployment should be as simple as possible. A single file deployment is best, but barring that a persistent environment (like the JVM or parrot) that doesn't need to change with a single file for the app's not bad either.

And I am taking a shot at being able to build a single-file combined interpreter and bytecode app, though it might be large... :)

[reply]

In Section Meditations