[16198] in Perl-Users-Digest
Perl-Users Digest, Issue: 3610 Volume: 9
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Mon Jul 10 20:09:25 2000
Date: Mon, 10 Jul 2000 17:09:14 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Message-Id: <963274154-v9-i3610@ruby.oce.orst.edu>
Content-Type: text
Perl-Users Digest Mon, 10 Jul 2000 Volume: 9 Number: 3610
Today's topics:
unlink() doesn't work for perl win32 <user@host.com>
Re: unlink() doesn't work for perl win32 (Michel Dalle)
Re: unlink() doesn't work for perl win32 <user@host.com>
Re: unlink() doesn't work for perl win32 newsposter@cthulhu.demon.nl
Re: unlink() doesn't work for perl win32 <bcaligari@shipreg.com>
Re: unlink() doesn't work for perl win32 <user@host.com>
Re: unlink() doesn't work for perl win32 <user@host.com>
Re: unlink() doesn't work for perl win32 <thoren@southern-division.com>
Re: unlink() doesn't work for perl win32 <Allan@due.net>
Re: unlink() doesn't work for perl win32 <Allan@due.net>
Re: unlink() doesn't work for perl win32 <lr@hpl.hp.com>
Re: unlink() doesn't work for perl win32 <user@host.com>
Re: unlink() doesn't work for perl win32 <Allan@due.net>
Re: unlink() doesn't work for perl win32 (Sam Holden)
Re: unlink() doesn't work for perl win32 <nnickee@nnickee.com>
Re: unlink() doesn't work for perl win32 <shcorey@nortelnetworks.com>
Re: unlink() doesn't work for perl win32 <nnickee@nnickee.com>
Re: unlink() doesn't work for perl win32 (Eric Bohlman)
Uploading picture files to server <k@idcnet.com>
Re: Uploading picture files to server <gus@black.hole-in-the.net>
Use of inherited AUTOLOAD: Error tmark@my-deja.com
Using carpout <ifalc@students.cs.mu.OZ.AU>
Re: Using carpout <tina@streetmail.com>
Digest Administrivia (Last modified: 16 Sep 99) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Thu, 06 Jul 2000 08:26:35 -0700
From: Bacbalabby <user@host.com>
Subject: unlink() doesn't work for perl win32
Message-Id: <3964A52B.264546FA@host.com>
Are there any alternatives?
------------------------------
Date: Thu, 06 Jul 2000 15:42:00 GMT
From: michel.dalle@usa.net (Michel Dalle)
Subject: Re: unlink() doesn't work for perl win32
Message-Id: <8k29hq$5bh$1@news.mch.sbs.de>
In article <3964A52B.264546FA@host.com>, Bacbalabby <user@host.com> wrote:
>Are there any alternatives?
It doesn't ? Strange...
Of course, it could be that you're trying to delete "c:\winnt\system.dat",
and Perl can't find 'c:winntsystem.dat'. Have you tried using / or \\ ?
Michel.
------------------------------
Date: Thu, 06 Jul 2000 09:02:36 -0700
From: Bacbalabby <user@host.com>
Subject: Re: unlink() doesn't work for perl win32
Message-Id: <3964AD9C.C7063105@host.com>
Maybe the problem is that I'm using Win98. I'm using the same convention for
passing a path to a function that I use everywhere else in my perl scripts,
tho the files are in the working directory; I've tried it without the path as
well.(I hate windows, I'd be in linux but the linux box is temporarily
unavailable)
Michel Dalle wrote:
> In article <3964A52B.264546FA@host.com>, Bacbalabby <user@host.com> wrote:
> >Are there any alternatives?
>
> It doesn't ? Strange...
>
> Of course, it could be that you're trying to delete "c:\winnt\system.dat",
> and Perl can't find 'c:winntsystem.dat'. Have you tried using / or \\ ?
>
> Michel.
------------------------------
Date: 6 Jul 2000 17:05:16 GMT
From: newsposter@cthulhu.demon.nl
Subject: Re: unlink() doesn't work for perl win32
Message-Id: <8k2e8c$f66$2@internal-news.uu.net>
Bacbalabby <user@host.com> wrote:
> Are there any alternatives?
`Doesn't work' is a worthless description. It doesn't tell us
anything useful. It only tells us that unlink doesn't do something
you want it to do. So tell us what you are trying to do in which
environment and how you are trying to do it, and what error message
you get.
If unlink really doesn't work for you, it should be possible to create
a very short example so we can see what you're doing wrong.
eg:
I'm trying to run the following code fragment:
unlink ("c:/Temp") || die "unlink failed:$!";
Instead of unlinking the file, it gives me the following error:
unlink failed:No such file or directory
Erik
------------------------------
Date: Thu, 6 Jul 2000 21:08:17 +0200
From: "Brendon Caligari" <bcaligari@shipreg.com>
Subject: Re: unlink() doesn't work for perl win32
Message-Id: <8k2krm$t5c$1@news.news-service.com>
"Bacbalabby" <user@host.com> wrote in message
news:3964A52B.264546FA@host.com...
> Are there any alternatives?
>
it does work!!!!!?????
------------------------------
Date: Thu, 06 Jul 2000 12:04:36 -0700
From: Bacbalabby <user@host.com>
Subject: Re: unlink() doesn't work for perl win32
Message-Id: <3964D844.E817112A@host.com>
Thanks I bet you couldn't think of a more respectful way phrase that than
"Doesn't work is a worthless description". I guarantee you wouldn't say it
that way to my face. But that's just the way the internet is I guess...
Anyway, uh, yeah was figuring most people would infer that "doesn't work on
win32, are there any alternatives" means "this feature of perl does not
function in windows(tho I should have said windows98), what else can I
use?" I'm not asking for you to tell me how to make unlink work. It
doesn't. I'm asking for alternatives for Windows 98. My question could not
have been more clear, I don't think.
newsposter@cthulhu.demon.nl wrote:
> Bacbalabby <user@host.com> wrote:
> > Are there any alternatives?
>
> `Doesn't work' is a worthless description. It doesn't tell us
> anything useful. It only tells us that unlink doesn't do something
> you want it to do. So tell us what you are trying to do in which
> environment and how you are trying to do it, and what error message
> you get.
>
> If unlink really doesn't work for you, it should be possible to create
> a very short example so we can see what you're doing wrong.
>
> eg:
> I'm trying to run the following code fragment:
> unlink ("c:/Temp") || die "unlink failed:$!";
> Instead of unlinking the file, it gives me the following error:
> unlink failed:No such file or directory
>
> Erik
------------------------------
Date: Thu, 06 Jul 2000 12:05:57 -0700
From: Bacbalabby <user@host.com>
Subject: Re: unlink() doesn't work for perl win32
Message-Id: <3964D895.48CD6512@host.com>
It doesn't, I know it's weird... I know *how* it works, b/c I use it in
Linux. On my Win98 machine though...
Brendon Caligari wrote:
> "Bacbalabby" <user@host.com> wrote in message
> news:3964A52B.264546FA@host.com...
> > Are there any alternatives?
> >
>
> it does work!!!!!?????
------------------------------
Date: Thu, 6 Jul 2000 21:26:25 +0200
From: "Thoren Johne" <thoren@southern-division.com>
Subject: Re: unlink() doesn't work for perl win32
Message-Id: <8k2mol$17u$14$1@news.t-online.com>
Bacbalabby <user@host.com> wrote in message
news:3964A52B.264546FA@host.com...
> Are there any alternatives?
sure there are:
unix,
linux,
solaris,
aix,
vms,
... etc.
gruß
thoren
8#X
--
----------------------------------------------------------------------
Thoren Johne - 8#X - thoren@southern-division.com
Southern Division Classic Bikes - www.southern-division.com
------------------------------
Date: Thu, 6 Jul 2000 15:37:21 -0400
From: "Allan M. Due" <Allan@due.net>
Subject: Re: unlink() doesn't work for perl win32
Message-Id: <8k2n6f$rtg$2@nntp9.atl.mindspring.net>
Bacbalabby <user@host.com> wrote in message news:3964D844.E817112A@host.com...
First please don't post jeopardy style with your response above the quoted
material. Posting after quoted material is a general Usenet convention and
strongly preferred in this newsgroup.
: Thanks I bet you couldn't think of a more respectful way phrase that than
: "Doesn't work is a worthless description". I guarantee you wouldn't say it
: that way to my face. But that's just the way the internet is I guess...
I believe he meant worthless in that it had no worth not as an insult, which
is how you seem to have take the comment. It has no worth because it is not
possible to understand your problem with the information provided. Unlink
functions as described in perlfunc under Win98 so your problem is likely
related to your code, your system configuration or something else. As we have
nothing else to work with other than "it does not work" it is not possible to
provide further assistance. The post you replied to does provide a suggestion
as to the type of information you could provide which would make assistance
more likely but you chose to ignore that advice.
: Anyway, uh, yeah was figuring most people would infer that "doesn't work on
: win32, are there any alternatives" means "this feature of perl does not
: function in windows(tho I should have said windows98), what else can I
: use?"
But it does work for others, so it is a logical inference is that you want the
functionality of unlink under windows, something that perl provides. The
logical conclusion would be to try to help you get unlink to work, but you
didn't provide enough information to provide that kind of assistance.
: I'm not asking for you to tell me how to make unlink work. It doesn't.
Ok, can't see why you have turned your back on unlink but maybe its personal
issue.
I'm asking for alternatives for Windows 98. My question could not
: have been more clear, I don't think.
Ok, alternatives that meet your very clear statement.
1. Use another language.
2. Use backticks and dos commands, possibly in a loop
3. Use system and dos commands, possibly in a loop
HTH
AmD
--
$email{'Allan M. Due'} = ' All@n.Due.net ';
--random quote --
Williams and Holland's Law: If enough data is collected, anything may be
proven by statistical methods.
------------------------------
Date: Thu, 6 Jul 2000 15:37:09 -0400
From: "Allan M. Due" <Allan@due.net>
Subject: Re: unlink() doesn't work for perl win32
Message-Id: <8k2n6e$rtg$1@nntp9.atl.mindspring.net>
Bacbalabby <user@host.com> wrote in message news:3964D844.E817112A@host.com...
First please don't post jeopardy style with your response above the quoted
material. Posting after quoted material is a general Usenet convention and
strongly preferred in this newsgroup.
: Thanks I bet you couldn't think of a more respectful way phrase that than
: "Doesn't work is a worthless description". I guarantee you wouldn't say it
: that way to my face. But that's just the way the internet is I guess...
I believe he meant worthless in that it had no worth not as an insult, which
is how you seem to have take the comment. It has no worth because it is not
possible to understand your problem with the information provided. Unlink
functions as described in perlfunc under Win98 so your problem is likely
related to your code, your system configuration or something else. As we have
nothing else to work with other than "it does not work" it is not possible to
provide further assistance. The post you replied to does provide a suggestion
as to the type of information you could provide which would make assistance
more likely but you chose to ignore that advice.
: Anyway, uh, yeah was figuring most people would infer that "doesn't work on
: win32, are there any alternatives" means "this feature of perl does not
: function in windows(tho I should have said windows98), what else can I
: use?"
But it does work for others, so it is a logical inference is that you want the
functionality of unlink under windows, something that perl provides. The
logical conclusion would be to try to help you get unlink to work, but you
didn't provide enough information to provide that kind of assistance.
: I'm not asking for you to tell me how to make unlink work. It doesn't.
Ok, can't see why you have turned your back on unlink but maybe its personal
issue.
I'm asking for alternatives for Windows 98. My question could not
: have been more clear, I don't think.
Ok, alternatives that meet your very clear statement.
1. Use another language.
2. Use backticks and dos commands, possibly in a loop
3. Use system and dos commands, possibly in a loop
HTH
AmD
--
$email{'Allan M. Due'} = ' All@n.Due.net ';
--random quote --
Williams and Holland's Law: If enough data is collected, anything may be
proven by statistical methods.
------------------------------
Date: Thu, 6 Jul 2000 12:49:36 -0700
From: Larry Rosler <lr@hpl.hp.com>
Subject: Re: unlink() doesn't work for perl win32
Message-Id: <MPG.13ce82ad7c22107a98abb0@nntp.hpl.hp.com>
In article <3964D895.48CD6512@host.com> on Thu, 06 Jul 2000 12:05:57 -
0700, Bacbalabby <user@host.com> says...
> It doesn't, I know it's weird... I know *how* it works, b/c I use it in
> Linux. On my Win98 machine though...
You keep saying that it doesn't work, but you have yet to show what the
actual diagnostic is. Others have already shown you how to do that,
using the $! special variable.
One possibility that distinguishes the file-system behavior on
Windows/DOS from that on Unix is that the file to be unlinked must not
be open. Other possibilities involve permissions. But without the
actual diagnostic, one can only conjecture.
--
(Just Another Larry) Rosler
Hewlett-Packard Laboratories
http://www.hpl.hp.com/personal/Larry_Rosler/
lr@hpl.hp.com
------------------------------
Date: Thu, 06 Jul 2000 13:04:35 -0700
From: Bacbalabby <user@host.com>
Subject: Re: unlink() doesn't work for perl win32
Message-Id: <3964E653.78DB8B6E@host.com>
> Ok, alternatives that meet your very clear statement.
>
> 1. Use another language.
> 2. Use backticks and dos commands, possibly in a loop
> 3. Use system and dos commands, possibly in a loop
Hey thanks! It was a clear question and you obviously understood it since I gave
no real extra information in my second post. The point is there's no way to be
more thorough with that question without insulting people's intelligence. You
guys know how unlink works--I *assume*--and I asked for an
alternative("...approach to the same or similar functionality" was hopefully
implied).
Also, thanks for letting me know about the convention for quoting in replies and
thanks for using "please". Sorry I didn't really read the rest of your post since
it bore no relevance to the question itself. But I appreciate your concern for
whatever it was about.
------------------------------
Date: Thu, 6 Jul 2000 16:11:19 -0400
From: "Allan M. Due" <Allan@due.net>
Subject: Re: unlink() doesn't work for perl win32
Message-Id: <8k2p66$82p$1@slb7.atl.mindspring.net>
Bacbalabby <user@host.com> wrote in message news:3964E653.78DB8B6E@host.com...
: > Ok, alternatives that meet your very clear statement.
: >
: > 1. Use another language.
: > 2. Use backticks and dos commands, possibly in a loop
: > 3. Use system and dos commands, possibly in a loop
:
: Hey thanks! It was a clear question and you obviously understood it since I
gave
: no real extra information in my second post. The point is there's no way
to be
: more thorough with that question without insulting people's intelligence.
You
: guys know how unlink works--I *assume*--and I asked for an
: alternative("...approach to the same or similar functionality" was hopefully
: implied).
If you want the right answer to the wrong question that's fine by me.
: Sorry I didn't really read the rest of your post since
: it bore no relevance to the question itself. But I appreciate your concern
for
: whatever it was about.
Well, I guess I will spend the same amount of effort reading your next post.
Sheesh.
--
$email{'Allan M. Due'} = ' All@n.Due.net ';
--random quote --
No rational argument will have a rational effect on a
man who does not want to adopt a rational attitude.
- Karl Popper
------------------------------
Date: 6 Jul 2000 19:36:36 GMT
From: sholden@pgrad.cs.usyd.edu.au (Sam Holden)
Subject: Re: unlink() doesn't work for perl win32
Message-Id: <slrn8m9nu4.l0r.sholden@pgrad.cs.usyd.edu.au>
On Thu, 06 Jul 2000 12:04:36 -0700, Bacbalabby <user@host.com> wrote:
>Thanks I bet you couldn't think of a more respectful way phrase that than
>"Doesn't work is a worthless description". I guarantee you wouldn't say it
>that way to my face. But that's just the way the internet is I guess...
That is exactly how I would say it to someone's face. Some indication
of what goes wrong, what error message occurs, etc is needed...
>Anyway, uh, yeah was figuring most people would infer that "doesn't work on
>win32, are there any alternatives" means "this feature of perl does not
>function in windows(tho I should have said windows98), what else can I
>use?" I'm not asking for you to tell me how to make unlink work. It
>doesn't. I'm asking for alternatives for Windows 98. My question could not
>have been more clear, I don't think.
So post the damn example as you were just asked to...
We all know that unlink works just fine on win98, thus you must be
doing something wrong.
We all have an idea of what you are doing wrong as well, but since you
refuse to post a one or two line sample that doesn't work you will just
have to work it out yourself.
--
Sam
It has been discovered that C++ provides a remarkable facility for
concealing the trival details of a program--such as where its bugs are.
--David Keppel
------------------------------
Date: Thu, 06 Jul 2000 18:17:46 -0500
From: Nnickee <nnickee@nnickee.com>
Subject: Re: unlink() doesn't work for perl win32
Message-Id: <A03ABC82CCC7A672.4EA472B0E2AF407E.C3A1C5CE6DADDD25@lp.airnews.net>
On Thu, 06 Jul 2000 12:04:36 -0700, someone claiming to be Bacbalabby
<user@host.com> said:
>Anyway, uh, yeah was figuring most people would infer that "doesn't work on
>win32, are there any alternatives" means "this feature of perl does not
>function in windows(tho I should have said windows98), what else can I
>use?" I'm not asking for you to tell me how to make unlink work. It
>doesn't. I'm asking for alternatives for Windows 98. My question could not
>have been more clear, I don't think.
I'm running win98 with ActivePerl, and unlink works just fine and
dandy here. Show us exactly what you're trying to do and tell us the
warning you got from $!
Nnickee
------------------------------
Date: Fri, 07 Jul 2000 09:08:03 -0400
From: Shawn Corey <shcorey@nortelnetworks.com>
Subject: Re: unlink() doesn't work for perl win32
Message-Id: <3965D633.8A852866@nortelnetworks.com>
Nnickee wrote:
>
> On Thu, 06 Jul 2000 12:04:36 -0700, someone claiming to be Bacbalabby
> <user@host.com> said:
>
> >Anyway, uh, yeah was figuring most people would infer that "doesn't work on
> >win32, are there any alternatives" means "this feature of perl does not
> >function in windows(tho I should have said windows98), what else can I
> >use?" I'm not asking for you to tell me how to make unlink work. It
> >doesn't. I'm asking for alternatives for Windows 98. My question could not
> >have been more clear, I don't think.
>
> I'm running win98 with ActivePerl, and unlink works just fine and
> dandy here. Show us exactly what you're trying to do and tell us the
> warning you got from $!
>
> Nnickee
I'm having the same problem. unlink does not seems to work with certain
file names.
unlink( 'C-1310-S1_3661_LB-DY59-Q1-7521.raw' ) or die "cannot unlink
C-1310-S1_3661_LB-DY59-Q1-7521.raw: $!\n";
prints:
cannot unlink C-1310-S1_3661_LB-DY59-Q1-7521.raw: Permission denied
I check the permissions of the file and all directories by to root, and
they are correct. I can delete the file either by Explorer or by MS DOS
prompt. Files with smaller file names don't seem to be a problem.
BTW, I'm running ActiveState perl v5.6 on Win98.
Shawn
------------------------------
Date: Fri, 07 Jul 2000 15:59:08 -0500
From: Nnickee <nnickee@nnickee.com>
Subject: Re: unlink() doesn't work for perl win32
Message-Id: <DAB1650FF8138FBC.1C868872670FF01F.9B98E1B54B10F578@lp.airnews.net>
On Fri, 07 Jul 2000 09:08:03 -0400, someone claiming to be Shawn Corey
<shcorey@nortelnetworks.com> said:
>I'm having the same problem. unlink does not seems to work with certain
>file names.
>unlink( 'C-1310-S1_3661_LB-DY59-Q1-7521.raw' ) or die "cannot unlink
>C-1310-S1_3661_LB-DY59-Q1-7521.raw: $!\n";
>prints:
>cannot unlink C-1310-S1_3661_LB-DY59-Q1-7521.raw: Permission denied
Is that file in the same directory as your script? Are you sure your
script is working in that same directory? Has your script opened that
file and not closed it yet when you're trying the unlink?
I just created a file, gave it that exact same name and unlinked it
using the exact snippet that you used above... and it deleted the
file.
So.. it would appear that your script is doing something else (like
opening the file and not closing it, etc.)
>I check the permissions of the file and all directories by to root, and
>they are correct. I can delete the file either by Explorer or by MS DOS
>prompt. Files with smaller file names don't seem to be a problem.
>BTW, I'm running ActiveState perl v5.6 on Win98.
Well, there's one difference between us - I'm using AS perl v 5.005_03
on Win98, so I guess it's possible that AS's 5.6 "broke" something in
the unlink command, but I'd still check everything over very carefully
before submitting a bug report about it.
Nnickee
------------------------------
Date: 7 Jul 2000 21:02:42 GMT
From: ebohlman@netcom.com (Eric Bohlman)
Subject: Re: unlink() doesn't work for perl win32
Message-Id: <8k5ghi$qd4$2@slb6.atl.mindspring.net>
Shawn Corey (shcorey@nortelnetworks.com) wrote:
: I'm having the same problem. unlink does not seems to work with certain
: file names.
: unlink( 'C-1310-S1_3661_LB-DY59-Q1-7521.raw' ) or die "cannot unlink
: C-1310-S1_3661_LB-DY59-Q1-7521.raw: $!\n";
: prints:
: cannot unlink C-1310-S1_3661_LB-DY59-Q1-7521.raw: Permission denied
:
: I check the permissions of the file and all directories by to root, and
: they are correct. I can delete the file either by Explorer or by MS DOS
: prompt. Files with smaller file names don't seem to be a problem.
"Permission denied" under Win32 often means that some process has the
file open at the time, which makes it impossible to delete the file
(since under Win32, unlinking always implies an immediate deletion). Is
it possible that your program opened the file but didn't close it before
trying to unlink it? (This is a good reason for getting in the habit of
explicitly closing files rather than relying on perl to do it as part of
exit-time cleanup.)
------------------------------
Date: Fri, 7 Jul 2000 02:54:40 -0500
From: "Kelly" <k@idcnet.com>
Subject: Uploading picture files to server
Message-Id: <1Zf95.1965$ef3.604313@homer.alpha.net>
Does anyone know how the person filling out a form can upload a picture file
from their computer to our server.
- Kelly
Kelly's Bar: http://www.kellys.com
------------------------------
Date: Fri, 07 Jul 2000 10:31:13 GMT
From: Gus <gus@black.hole-in-the.net>
Subject: Re: Uploading picture files to server
Message-Id: <962965873.5309.1.nnrp-01.c29f015a@news.demon.co.uk>
Kelly <k@idcnet.com> wrote:
> Does anyone know how the person filling out a form can upload a picture file
> from their computer to our server.
That is not a Perl question, you want comp.infosystems.www.authoring.cgi
perldoc CGI will help though.
Regards,
_Gus
--
gus@black.hole-in-the.net
0x58E18C6D
82 AA 4D 7F D8 45 58 05 6D 1B 1A 72 1E DB 31 B5
http://black.hole-in-the.net/gus/
------------------------------
Date: Tue, 04 Jul 2000 20:10:06 GMT
From: tmark@my-deja.com
Subject: Use of inherited AUTOLOAD: Error
Message-Id: <8jtgal$t7s$1@nnrp1.deja.com>
Hi All,
I have a module in which I am trying to include some non-method
routines, i.e. routines which aren't called as a method of an object,
but are called directly. In my case, these are routines which don't
necessarily make sense as a method of an object, but are useful to have
around whenever you happen to be working with a given class. None of
these non-method routines expect to inherit anything.
However, when trying to invoke the routine directly, as in
$x = newmodule::get_name ();
I get this warning:
Use of inherited AUTOLOAD for non-method newmodule::get_name() is
deprecated at (...)
Adding use diagnostics to the head of the calling code, I get more
verbose notes (following). What is germane is that the note *says* the
'bug' will be rectified in perl 5.005, but does not seem to be (I am
running 5.005_03). What can I do to avoid this condition ? (Or as a
worst case, how can I at least suppress the error message :))
Thanks - any help is much appreciated !
terry
(D) As an (ahem) accidental feature, AUTOLOAD subroutines are looked
up as methods (using the @ISA hierarchy) even when the subroutines
to
be autoloaded were called as plain functions (e.g. Foo::bar()), not
as methods (e.g. Foo-bar()> or $obj-bar()>).
This bug will be rectified in Perl 5.005, which will use method
lookup
only for methods' AUTOLOADs. However, there is a significant base
of existing code that may be using the old behavior. So, as an
interim step, Perl 5.004 issues an optional warning when non-methods
use inherited AUTOLOADs.
The simple rule is: Inheritance will not work when autoloading
non-methods. The simple fix for old code is: In any module that
used to
depend on inheriting AUTOLOAD for non-methods from a base class
named
BaseClass, execute *AUTOLOAD = \&BaseClass::AUTOLOAD during startup.
In code that currently says use AutoLoader; @ISA = qw(AutoLoader);
you
should remove AutoLoader from @ISA and change use AutoLoader; to
use AutoLoader 'AUTOLOAD';.
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
Date: Tue, 4 Jul 2000 02:27:55 +1000
From: Ian FALCAO <ifalc@students.cs.mu.OZ.AU>
Subject: Using carpout
Message-Id: <Pine.GSO.4.05.10007040218081.7663-100000@holly.cs.mu.OZ.AU>
Hello
Does anyone know how to use the carpout function in a script using an
object oriented approach. I tried the suggestions in the CGI::Carp manual
i.e. use CGI::Carp qw(carpout); but and some other ways but they all still
report carpout as being undefined.
Basically i just want to display anything stderr prints at the unix prompt
in the browser.
I would be greatful for any help
Thanks
Ian
------------------------------
Date: 4 Jul 2000 00:04:35 GMT
From: Tina Mueller <tina@streetmail.com>
Subject: Re: Using carpout
Message-Id: <8jr9mj$15knk$2@ID-24002.news.cis.dfn.de>
hi,
Ian FALCAO <ifalc@students.cs.mu.oz.au> wrote:
> Does anyone know how to use the carpout function in a script using an
> object oriented approach. I tried the suggestions in the CGI::Carp manual
> i.e. use CGI::Carp qw(carpout); but and some other ways but they all still
> report carpout as being undefined.
hm, this should work. what exactly did you try?
> Basically i just want to display anything stderr prints at the unix prompt
> in the browser.
then it would just be enough using the fatalsToBrowser:
use CGI::Carp qw{fatalsToBrowser};
tina
--
http://tinita.de \ enter__| |__the___ _ _ ___
tina's moviedatabase \ / _` / _ \/ _ \ '_(_-< of
search & add comments \ \ _,_\ __/\ __/_| /__/ perception
"The Software required Win98 or better, so I installed Linux."
------------------------------
Date: 16 Sep 99 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 16 Sep 99)
Message-Id: <null>
Administrivia:
The Perl-Users Digest is a retransmission of the USENET newsgroup
comp.lang.perl.misc. For subscription or unsubscription requests, send
the single line:
subscribe perl-users
or:
unsubscribe perl-users
to almanac@ruby.oce.orst.edu.
| NOTE: The mail to news gateway, and thus the ability to submit articles
| through this service to the newsgroup, has been removed. I do not have
| time to individually vet each article to make sure that someone isn't
| abusing the service, and I no longer have any desire to waste my time
| dealing with the campus admins when some fool complains to them about an
| article that has come through the gateway instead of complaining
| to the source.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
To request back copies (available for a week or so), send your request
to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
where x is the volume number and y is the issue number.
For other requests pertaining to the digest, send mail to
perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
sending perl questions to the -request address, I don't have time to
answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V9 Issue 3610
**************************************
