Re^4: Perl 6 ... dead? (no, just convalescing)

Comment on Re^4: Perl 6 ... dead? (no, just convalescing)
Re^5: Perl 6 ... dead? (no, just convalescing) by Anonymous Monk on Sep 01, 2004 at 08:02 UTC
Yes it is	[reply]
Re^6: Perl 6 ... dead? (no, just convalescing) by Wassercrats on Sep 01, 2004 at 19:00 UTC
Is not. Real bytecode ads an extra level of protection. It's more difficult to understand.	[reply]
Re^7: Perl 6 ... dead? (no, just convalescing) by Ven'Tatsu (Deacon) on Sep 01, 2004 at 20:01 UTC
You can convert your Perl 5 scripts to bytecode, and any one can -MO=Deparse them back to something (reasonably) close to the original code. In Perl 6 you will (I assume) be able to convert your scripts to byte code tartgeting Parrot, and some one will eventualy make a Deparser for Parrot/Perl 6. Perl 6 will probably not be that much friendlier to source hiding than Perl 5 is. You could always try B::C if your willing to give up some portability.	[reply]
Re^8: Perl 6 ... dead? (no, just convalescing) by Wassercrats on Sep 01, 2004 at 20:23 UTC
Re^9: Perl 6 ... dead? (no, just convalescing) by QM (Vicar) on Sep 02, 2004 at 17:04 UTC
Some notes below your chosen depth have not been shown here
Re^8: Perl 6 ... dead? (no, just convalescing) by osfameron (Hermit) on Sep 02, 2004 at 08:33 UTC
Re^5: Perl 6 ... dead? (no, just convalescing) by Anonymous Monk on Sep 01, 2004 at 18:20 UTC
Having reviewed VarStructor, I think you need a way to protect your code from being executed as well. Technically speaking, I think deletion fulfills both of our requirements of your code.	[reply]
Re^6: Perl 6 ... dead? (no, just convalescing) by Wassercrats on Sep 01, 2004 at 18:59 UTC
Your reply is at Re: VarStructor 1.0.	[reply]


Keep It Simple, Stupid
	PerlMonks

Re^4: Perl 6 ... dead? (no, just convalescing)

The best material for plates (tableware) is: