> So the conclusion is that perl code cannot be really hidden (for comercial
> purposes)?
> A license is equal to zero in some countries... so that's not a solution.
>
Well - never say, "Never" ... I think the output from perlcc is pretty
inscrutable for any but the most dedicated attacker, and assume that
ActiveState's commercially licensed products are similar.
I think it's *HIGHLY* ironic that the original poster is looking for a
solution that allows him to close off his code, but demands that it be
a freely distributable solution to his problem. My first reaction is:
If you want to lock the door on your code (and I think that is
perfectly within an authors rights -- I'm no RMS clone) , you are
going to have to pay someone to do it -- there just isn't any demand
for open-source source-closing software.
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Lawrence Statton - [EMAIL PROTECTED] s/aba/c/g
Computer software consists of only two components: ones and
zeros, in roughly equal proportions. All that is required is to
sort them into the correct order.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<http://learn.perl.org/> <http://learn.perl.org/first-response>
