develooper Front page | perl.bootstrap | Postings from July 2000

Re: Obscuring code?

Thread Previous | Thread Next
From:
Dan Sugalski
Date:
July 25, 2000 20:32
Subject:
Re: Obscuring code?
Message ID:
4.3.2.7.0.20000725231312.00e1c250@24.8.96.48
At 02:22 PM 7/25/00 -0700, phil@Stimpy.netroedge.com wrote:

>I don't know if this has been covered or not (I just subscribed and
>didn't see an archive for the list), but I'd like to propose some
>method, whether built into Perl6 or completely external, to provide
>obscuring of source code.

I've never seen the point in this, but all the jobs I've worked at have 
been with packages where the clients all have source, either because the 
vendor abandoned the market and the failsafe license clauses kicked in, or 
because the vendor was expecting the clients to go and fix all the 
fundamental design flaws. (Features! I meant features! Really... :) Having 
said that, I really don't care, and it's certainly possible to do now. 
(It'd take some fancy XS footwork, but it can be done, and with something 
more secure than filters)

It's not inconceivable that perl 6 will end up emitting, at some stage of 
the game, a stream of data that is a fully functioning program but can't be 
reasonably turned back into perl source. A heavily optimizing bytecode 
compiler may do this, as would a backend that emitted java bytecode. 
*Specifically* designing this feature in will require either replacing me, 
or an Edict From Larry. I will not, however, trade execution speed for the 
ability to do decompilation.

					Dan

--------------------------------------"it's like this"-------------------
Dan Sugalski                          even samurai
dan@sidhe.org                         have teddy bears and even
                                      teddy bears get drunk


Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About