Ernst Rohlicek jun. wrote:
>
>
> Hi everbody,
>
> I got into Perl yesterday for using a Perl extension for PVM, a parallel
> computing environment, but found out that some newer functions were not
> yet in it.
>
> So, I added to the extension, but so far I couldn't figure out wrapping
> a more
Hi everbody,
I got into Perl yesterday for using a Perl extension for PVM, a parallel
computing environment, but found out that some newer functions were not
yet in it.
So, I added to the extension, but so far I couldn't figure out wrapping
a more complex function.
The C function pvm_getmbox
From: "R. Joseph Newton" <[EMAIL PROTECTED]>
> Jenda Krynicky wrote:
> > No. The original distinction between *.pl and *.plx was the
> > interpreter used for CGIs.
> > The *.pl was interpreted by perl.exe, while *.plx was interpreted by
> > perlIS.dll (In-process Perl interpreter for MS IIS).
>
>
Jenda Krynicky wrote:
> > > > "fyi
> > > > .pl used to be used for both executables and libraries.
> > > > A library is simply perl code located in a different file
> > > > which is imported into another perl program with the 'require'
> > > > keyword.
> > > >
> > > > Now t
From: Tassilo von Parseval <[EMAIL PROTECTED]>
> On Fri, Jun 06, 2003 at 10:33:21PM -0700 R. Joseph Newton wrote:
> > Francis Henry wrote:
> > > The following is a note from a colleague of which I am skeptical:
> > >
> > > "fyi
> > > .pl used to be used for both executables and libraries.
>
On Fri, Jun 06, 2003 at 10:33:21PM -0700 R. Joseph Newton wrote:
> Francis Henry wrote:
> > The following is a note from a colleague of which I am skeptical:
> >
> > "fyi
> > .pl used to be used for both executables and libraries.
> > A library is simply perl code located in a differe
Francis Henry wrote:
> Hi:
>
> The following is a note from a colleague of which I am skeptical:
>
> "fyi
> .pl used to be used for both executables and libraries.
> A library is simply perl code located in a different file which is
> imported into another perl program with the 're
On Friday, June 6, 2003, at 11:27 AM, Francis Henry wrote:
Thanks Aman. I think I understand what he's trying to do - I'm more
concerned
that this is the common practice with perl and I wasn't aware of it.
Know what
I mean?
I've at least heard of it before, if that tells you anything. I
bel
t;
> - Original Message -
> From: "Francis Henry" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, June 06, 2003 10:29 AM
> Subject: perl extensions
>
> > Hi:
> >
> > The following is a note from a colleague of which I am skept
with extension .pl
Aman Raheja
- Original Message -
From: "Francis Henry" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 06, 2003 10:29 AM
Subject: perl extensions
> Hi:
>
> The following is a note from a colleague of which I am skeptica
Hi:
The following is a note from a colleague of which I am skeptical:
"fyi
.pl used to be used for both executables and libraries.
A library is simply perl code located in a different file which is
imported into another perl program with the 'require' keyword.
Now that we hav
On Fri, Nov 01, 2002 at 11:15:15AM -0800, George Szynal wrote:
> For those who want/need to install a Perl app or extension without perturbing the
>default perl library tree.
> Possible reasons:
>1. Disambiguating the existing libs from your libs (for testing perhaps)
>2. Not wanting to or
Thank you.
George Szynal <[EMAIL PROTECTED]> wrote:For those who want/need to install a
Perl app or extension without perturbing the default perl library tree.
Possible reasons:
1. Disambiguating the existing libs from your libs (for testing perhaps)
2. Not wanting to or not having rights to log
For those who want/need to install a Perl app or extension without perturbing the
default perl library tree.
Possible reasons:
1. Disambiguating the existing libs from your libs (for testing perhaps)
2. Not wanting to or not having rights to login as a supervisor (or as a user with
admin ri
14 matches
Mail list logo
