On Tue, Sep 14, 2004 at 07:40:37AM +0300, Gaal Yahas wrote:
Anyway, since most systems don't have it either, I almost always put -w
on the #! line even if my script is bound to run on 5.8, which supports
the warnings pragma, to exploit the behavior you encountered here. Looks
like I wasn't
Abigail wrote:
On Tue, Sep 14, 2004 at 07:40:37AM +0300, Gaal Yahas wrote:
Anyway, since most systems don't have it either, I almost always put -w
on the #! line even if my script is bound to run on 5.8, which supports
the warnings pragma, to exploit the behavior you encountered here. Looks
like I
Gaal Yahas writes:
On Mon, Sep 13, 2004 at 10:53:55PM -, Smylers [EMAIL PROTECTED]
wrote:
And that breaks things, cos perl^M isn't something that BSD can execute.
Of course it is something that BSD can execute. You just don't happen
to have an executable called perl^M in /usr/bin/.
Bart Lateur [EMAIL PROTECTED] wrote:
Not fun but...
Use
local $^W;
near where the bulk of the warnings are coming from, assuming
it's safe to be ignored, maybe just these lines in their own
block.
Or just initialize the variables and avoid the warnings.
Still not fun, though.
--
A. Pagaltzis writes:
* Smylers [EMAIL PROTECTED] [2004-08-04 00:34]:
[*0] It was cluttering up the error log with benign 'uninitialized'
messages, which were obscuring the output (from some other script)
that I wanted to see.
Maybe you can try just disabling those?
no
I turned warnings off in a script[*0] but made no other changes to it.
This broke the script, in that it would no longer run correctly[*1]. In
other circumstances[*2] I might've regarded this as fun.
Presuming that this isn't a well-known situation, can anybody guess how
it's done?
[*0] It
* Smylers [EMAIL PROTECTED] [2004-08-04 00:34]:
[*0] It was cluttering up the error log with benign 'uninitialized'
messages, which were obscuring the output (from some other script)
that I wanted to see.
Maybe you can try just disabling those?
no warnings 'uninitialized';
On Tue, Aug 03, 2004 at 06:12:25PM +, Smylers wrote:
I turned warnings off in a script[*0] but made no other changes to it.
This broke the script, in that it would no longer run correctly[*1]. In
other circumstances[*2] I might've regarded this as fun.
Presuming that this isn't a
