compiled perl question.

[DaLoverhino]

I read somewhere that perl gets compiled to bytecodes and is run in a
perl virtual machine similar to Java. Is that true? What I'd like to
do is give a bytecode compiled version of my perl script, but not the
script itself, to prevent copying or modifying it. I'd rather not run
the script through an obfuscator.

Can this be done? And how?

Can you point me to a link?

thanks.

 

[Jürgen Exner]

I read somewhere that perl gets compiled to bytecodes and is run in a
perl virtual machine similar to Java. Is that true? What I'd like to
do is give a bytecode compiled version of my perl script, but not the
script itself, to prevent copying or modifying it. I'd rather not run
the script through an obfuscator.

perldoc -q hide

How can I hide the source for my Perl program?

jue

 

[DaLoverhino]

perldoc -q hide

  How can I hide the source for my Perl program?

jue

Thanks, unfortunately, I don't have perldoc on my system, and I am not
the sys admin of our unix boxes. Can you copy/past the output of that
command for me onto this thread, please? Thanks.

 

[Jürgen Exner]

Thanks, unfortunately, I don't have perldoc on my system,

I don't understand. perldoc is part of Perl. If it isn't installed then
your Perl installation is broken. Maybe fix it?

And how do you manage to program in Perl at all without the
documentation being available? How are you looking up the functionality
of an operator or checking the meaning of a predefined variable or
confirming which type of arguments a function takes?

and I am not the sys admin of our unix boxes.

Why don't you create your own installation of Perl instead of using a
broken one?

Can you copy/past the output of that
command for me onto this thread, please? Thanks.

That would be against all Usenet ettiquette, but here's a web link:
http://perldoc.perl.org/perlfaq3.html#How-can-I-hide-the-source-for-my-Perl-program?

jue

 

[DaLoverhino]

If you can't write any executable files anywhere to any filesystem
(which is the only possible explanation for not being able to install a
private copy of perldoc) how can you even produce any code at all?

I guess because perldoc is 32mb file, and I don't have the space on my
account. Using the keyword 'hide', I was able to find some links.
Thanks for the help.

 

[ccc31807]

 What I'd like to
do is give a bytecode compiled version of my perl script, but not the
script itself, to prevent copying or modifying it.  I'd rather not run
the script through an obfuscator.

Look at perlcc. I've used it to generate an exe file on Linux, but
it's real ugly and results in a very large file.

CC

 

[Jürgen Exner]

I guess because perldoc is 32mb file, and I don't have the space on my
account.

I think you meant 32MB, not 32 millibar.

Owwww, wait a second. Are we living in the same year? 1TB drives go for
just over about 100$ US nowadays. That translates into those 32MB
costing about 0.32 Cent US. Are you saying your employer or university
or whoever owns those machines cannot afford 1/3 of a cent to have a
working Perl installation? But they can afford their employees writing
programs without having the documentation they need.
I had not idea the economic crisis was that bad.

jue

 

[A. Sinan Unur]

I think you meant 32MB, not 32 millibar.

Owwww, wait a second. Are we living in the same year? 1TB drives go
for just over about 100$ US nowadays. That translates into those 32MB
costing about 0.32 Cent US. Are you saying your employer or university
or whoever owns those machines cannot afford 1/3 of a cent to have a
working Perl installation? But they can afford their employees writing
programs without having the documentation they need.
I had not idea the economic crisis was that bad.

I guess it would be too much to hope that he would have access to some
other computer where he could install the corresponding version of Perl
with documentation and everything.

I mean, computers are giant water-cooled cabinets housed in a big
concrete windowless building. I did some work in one of those about 25
years ago.

There is no excuse for not having a system with a full installation of
Perl even if your sysadmins are willing to live with a completely borked
installation of Perl.

Sinan

--
A. Sinan Unur <[email protected]>
(remove .invalid and reverse each component for email address)

comp.lang.perl.misc guidelines on the WWW:
http://www.rehabitation.com/clpmisc/

 

[News123]

http://perldoc.perl.org/

Just enter hide into the search field.

HOWEVER. Be aware, that the documentation might be for a different per
version than yours. For some new features you might find discerpancies.


Below the search field you can select the two previous main perl versions.



N.

 

[Tassilo von Parseval]

Thus spake Sherm Pendley:

That kind of brokenness is sadly common among Linux distributions. Many
of them separate Perl's 'perldoc' script and '*.pod' files into a -dev
package that must be installed separately.

Which happens to make perfect sense. As much as we Perl purists may
despise it, I certainly welcome not having to install all the utility
junk belonging to languages I do not program in (Python, Ruby etc.) when
all I need is the core of it to satisfy some dependency of another
package.

All of this is of course blatantly off-topic.

Cheers,
Tassilo

 

[Jürgen Exner]

Thus spake Sherm Pendley:

Which happens to make perfect sense. As much as we Perl purists may
despise it, I certainly welcome not having to install all the utility
junk belonging to languages I do not program in (Python, Ruby etc.) when
all I need is the core of it to satisfy some dependency of another
package.

Fair enough. But _WHEN_ you program in language X then the documentation
for that language does become a vital part of the installation.

All of this is of course blatantly off-topic.

Not really. Programming in Perl without using the proper documentation
for the installed version of Perl is IMO on-topic for this NG.
Advise: just don't do it.

jue