-boun...@listserv.activestate.com
Subject: RE: Issue with Mail::Sender : "what is the << function called?"
> > ... but what exactly is the "<<" function called?
>
> It's called a "here doc" - it's a unix/shell conventio
> ... but what exactly is the "<<" function called?
It's called a "here doc" - it's a unix/shell convention, allowing
multiline input:
$ mail root < hi
>
> mom
>
> .
> EOM
(old 'mail' ends w/ a '.' on line by
please forgive my ignorance, but what exactly is the "<<" function called?
Ive tried to search the net for "perl" and "<<" and cant seem to find
anything about this?
-Original Message-
From: perl-win32-users-boun...@listserv.act
On Tue, 01 Apr 2008, Howard Maher wrote:
> One of our possible vendors said that if Perl scripts can be callable
> COM objects, then we can interface with their engine. Does anyone know
> whether Perl scripts can be? The languages that they suggest are VB6,
> C++, and .NET...
Perl code can be wrap
Howard Maher wrote:
> One of our possible vendors said that if Perl scripts can be callable COM
> objects, then we can interface with their engine. Does anyone know whether
> Perl scripts can be? The languages that they suggest are VB6, C++, and
> .NET... The Perl.NET project has pretty much
One of our possible vendors said that if Perl scripts can be callable COM
objects, then we can interface with their engine. Does anyone know whether
Perl scripts can be? The languages that they suggest are VB6, C++, and .NET...
The Perl.NET project has pretty much been scrapped, correct? Th
> my (@parm) = @_;
> my ($pkg, $filename, $line, $subname) = called;
> log_debug("$subname start, number of parm = ", scalar(@parm), "\n";
> ...
> }
>
> If not possible I must code like;
> ...
> sub sub_1 {
> my (@parm) = @_;
> my $subID =
Hi,
Is there Perl built-in function, the reverse of "caller"?
Now I'm coding many many subroutines.
I like to get current name of subroutine just I'm in.
...
sub sub_1 {
my (@parm) = @_;
my ($pkg, $filename, $line, $subname) = called;
log_debug("$subname start, n
On Fri, 12 Jan 2001, Ron Pero wrote:
> Dear All
>
> Have followed the thread on Redirect the output of a system function.
>
> I thought I had this down, but have just gotten stumped. I cannot get the
> output of a call to useradd.
>
> This is on a Linux/bash box.
> Have tried the following, bu
At 01:40 PM 01/12/01 -0800, you wrote:
>Ron Pero wrote:
>>
>> my $x = `useradd -c $company -m $username`;
>> print "\$x = $x";
>>
>> When I run the script, the shell outputs the message:
>> useradd: user rmartino exists
>> but I want to test $x. If the user already exists, I want to stop program
Bill,
Yes, I'd noticed that under 62x, the compiler MUST see the subroutine
definition before it see the first call, or it gives that warning. The %2x
builds didn't do this.
Merrill
> Could be a 623 bug, works fine under 522. What version are you using?
> Can't find that error in man pages for
Marcus wrote:
>
> Can anybody explain the cause of the following warning?
>
> "File::Recurse::recurse() called too early to check prototype at
> C:/Perl56/site/lib/File/Recurse.pm line 49."
>
> I tried declaring the sub and using an ampersand for recurse.
Marcus wrote, on Thursday, January 11, 2001 07:24
: Can anybody explain the cause of the following warning?
:
: "File::Recurse::recurse() called too early to check prototype at
: C:/Perl56/site/lib/File/Recurse.pm line 49."
:
: I tried declaring the sub and using an ampersand f
Can anybody explain the cause of the following warning?
"File::Recurse::recurse() called too early to check prototype at
C:/Perl56/site/lib/File/Recurse.pm line 49."
I tried declaring the sub and using an ampersand for recurse. Here's my
code:
use File::Recurse;
$local_base
14 matches
Mail list logo
