Jenda Krynicky said:
> From: "Paul Johnson" <[EMAIL PROTECTED]>
>> As I recall, someone (Timothy Johnson?) said they got errors from
>> using Win32 more than once and resorted to requiring it to silence the
>> errors. I don't think we ever saw the error messages or the code.
>> This prompted me t
From: "Paul Johnson" <[EMAIL PROTECTED]>
> As I recall, someone (Timothy Johnson?) said they got errors from
> using Win32 more than once and resorted to requiring it to silence the
> errors. I don't think we ever saw the error messages or the code.
> This prompted me to write the first paragraph
Jenda Krynicky said:
> From: "Paul Johnson" <[EMAIL PROTECTED]>
>> It sounds like something is broken in the Win32 import sub (I have
>> never used or looked at Win32.pm), or that there is some other
>> problem, but import guards are not the solution.
>
> No there is nothing broken. The modules A
From: "Paul Johnson" <[EMAIL PROTECTED]>
> R. Joseph Newton said:
> > worry about that at all. In C/C++, one of the standards for writing
> > any header file is to always surround the entirety with an inclusion
> > guard to prevent the precompiler from redefining classes or
> > redeclarating other
R. Joseph Newton said:
>> And that finally explains why in some of my scripts using the
>> Win32::Lanman
>> module I have to do a 'require Win32;' instead of a 'use Win32' if I
>> don't
>> want to get warning messages about conflicting constants.
>
> I*t sems to me that this is sort of a shortcom
Timothy Johnson wrote:
> I agree, but I'm not quite to the point where I can go back and fix it
> myself.
Yes, you can. That's why Perl modules are open source.
If you want to be less radical, open the pm, find at least one constant it defines,
and surround your use statements with similar, bu
I agree, but I'm not quite to the point where I can go back and fix it
myself.
-Original Message-
From: R. Joseph Newton [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 23, 2003 9:53 PM
To: Timothy Johnson
Cc: 'Dan Muey'; Rob Dixon; [EMAIL PROTECTED]
Subject: Re: Multi
> And that finally explains why in some of my scripts using the Win32::Lanman
> module I have to do a 'require Win32;' instead of a 'use Win32' if I don't
> want to get warning messages about conflicting constants.
I*t sems to me that this is sort of a shortcoming, if you have to worry about that
Thanks I'll do that.
>
> From: "Dan Muey" <[EMAIL PROTECTED]>
> > Here's something I've been wondering
> >
> > What kind of performance issues are there if you do a 'use' on the
> > same module in the same script twice or more?
>
> Depends.
> This can be verry different for different modul
From: "Dan Muey" <[EMAIL PROTECTED]>
> Here's something I've been wondering
>
> What kind of performance issues are there if you do a 'use' on the
> same module in the same script twice or more?
Depends.
This can be verry different for different modules.
use Module;
does two things:
I'll figure out why when I get some extra
time" issues. I love it when the light bulb finally comes on.
-Original Message-
From: Dan Muey [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 23, 2003 9:37 AM
To: Rob Dixon; [EMAIL PROTECTED]
Subject: RE: Multiple use of same module que
So I don't have to worry about doing use Module; or
varitions of it like use Module stuffdealy; more than once causing performance issues?
Great, thanks that's load off!
Dan
>
> Hi Dan
>
> Dan Muey wrote:
> > Here's something I've been wondering
> >
> > What kind of performance issues ar
Hi Dan
Dan Muey wrote:
> Here's something I've been wondering
>
> What kind of performance issues are there if you do a 'use' on the
> same module in the same script twice or more?
I posted the following earlier today in response to a question of
Beau's:
Rob Dixon wrote:
> Beau E. Cox wrote:
Here's something I've been wondering
What kind of performance issues are there if you do a 'use' on the same module in the
same script twice or more?
Before you go ' Well that's stupid, why would you do that? ' let me explain :
Script one has
use CGI;
require stumpy.lib;
stumpy_funtion
14 matches
Mail list logo
