You can also look at PAR... http://www.autrijus.org/par-intro/
Sumit.
<<<>>> <<<>>> <<<>>> <<<>>> <<<>>> <<<>>> <<<>>> <<<>>> <<<>>> <<<>>>
We cannot become what we need to be by remaining what we are.
<<<>>> <<<>>> <<<>>> <<<>>> <<<>>> <<<>>> <<<>>> <<<>>> <<<>>> <<<>>>
Toby Stuart
<toby.stuart@figtrees To: "'[EMAIL PROTECTED]'"
<[EMAIL PROTECTED]>
ys.com.au> cc:
Subject: RE: Securing/Encrypting
Source
08-11-2002 09:42 AM
how about the poor mans way ... Acme::Bleach
> -----Original Message-----
> From: Timothy Johnson [mailto:tjohnson@;sandisk.com]
> Sent: Friday, November 08, 2002 11:05 AM
> To: 'dan'; [EMAIL PROTECTED]
> Subject: RE: Securing/Encrypting Source
>
>
>
> If you just want to make it harder, you can try "compiling"
> it with PerlApp
> from ActiveState. Bear in mind, this will not make it
> impossible to see
> your source, but it will make it difficult, since the source
> IS visible in
> memory while your scripts are executing.
>
> -----Original Message-----
> From: dan [mailto:mail@;danneh.demon.co.uk]
> Sent: Friday, November 08, 2002 11:13 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Securing/Encrypting Source
>
>
> so if perlcc is not a good way to compile your perl source
> for *nix systems,
> then what is?
>
> dan
>
> "Paul Johnson" <[EMAIL PROTECTED]> wrote in message
> news:20021107205443.GA4209@;pjcj.net...
> > On Thu, Nov 07, 2002 at 03:08:23PM -0000, dan wrote:
> >
> > > answering my own question, i read back the newsgroup a
> little, and came
> > > across an article about perlcc. i tried this..
> > > perlcc -o output input.pl
> > > however, since my program uses DBI, the end compiled
> program reads:
> > >
> > > Connecting to SQL...
> > > Undefined subroutine &DBI::dr::connect called at
> > > /usr/local/lib/perl5/site_perl/5.8.0/i686-linux/DBI.pm line 503.
> > > Undefined subroutine &DBI::dr::disconnect_all called at
> > > /usr/local/lib/perl5/site_perl/5.8.0/i686-linux/DBI.pm line 565.
> > > END failed--call queue aborted.
> > >
> > > any ideas how i may be able to come over this?
> >
> > Two.
> >
> > 1. Forget you ever heard about perlcc.
> > 2. Prepare for some heavy duty hacking.
> >
> > perlcc is experimental, incomplete and buggy and that looks
> unlikely to
> > change in the near future.
> >
> > --
> > Paul Johnson - [EMAIL PROTECTED]
> > http://www.pjcj.net
>
>
>
> --
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> --
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
