--- Original Message ---
> Ted Fines wrote:
> > Hi,
>
> Hello,
>
> > I'm running into a Cach-22 with 'use strict', and filehandles.
> >
> > I have a program which opens two log files at the beginning:
> > open(INFLOG,">>$info_log") || die "Could not append to $info_log_file.
> > Quitting.\n";
Ted Fines wrote:
> Hi,
Hello,
> I'm running into a Cach-22 with 'use strict', and filehandles.
>
> I have a program which opens two log files at the beginning:
> open(INFLOG,">>$info_log") || die "Could not append to $info_log_file.
> Quitting.\n";
> open(ERRLOG,">>$error_log") || die "Could n
If you want to pass a filehandle like that I would recommend using the
FileHandle module.
As your script stands, however, you have no reason to pass the
filehandle to the subroutine. You can just do a "print ERRLOG $scalar"
to print.
-Original Message-
From: Ted Fines [mailto:[EMAIL
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (B McKee) writes:
>On Tuesday, January 20, 2004, at 10:34 AM, B McKee wrote:
>
>> Hi All,
>> I'm having trouble understanding what use strict is trying to tell me.
>> If I have run this program
>...snipped
>> open(MESSAGE, "$datafile") or die "Can
On Tuesday, January 20, 2004, at 10:34 AM, B McKee wrote:
Hi All,
I'm having trouble understanding what use strict is trying to tell me.
If I have run this program
...snipped
open(MESSAGE, "$datafile") or die "Cannot open datafile: $!";
while (!eof(MESSAGE)) {
$page = new CGI(MESSAGE);
...mor
I had a similar problem passing a filehandle to a sub and learned that I had to use
the typeglob instead.
HTH,
Jan
B McKee wrote:
>Hi All,
>I'm having trouble understanding what use strict is trying to tell me.
>
>If I have run this program
>
>-CODE---
>#!/u
Ah, ok, thats it,
but by now I rewrote it with my $compu = new FileHandle, but I'm in rouble
with getc or sysread operations on the handle. I'll put a commented working
version on my hp: Jan-Kirchhoff.de asap.
thanks for the help to everybody,
Jan
Am Sonntag, 28. Oktober 2001 04:12 schrieb [EMA
IIRC the warning is intentionally suppressed if the alleged 'reserved
word' is uppercase, i.e. it will complain about "open f,$file" but
not "open F, $file".
On Sat, 27 Oct 2001, Jan wrote:
> Date: Sat, 27 Oct 2001 20:39:48 +0200
> From: Jan <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject:
On Sat, 27 Oct 2001, Jan wrote:
> sub open
> {
> open("compu","+<$port") || die "opening $port failed: $!";
> system("stty 19200 -echo cstopb cbreak -parenb cs8 parodd < $port");
> compu->autoflush(1);
> print "\nopened interface on port --> $port\n";
> }
Where I am getting confused is how you a
Uh, ok, wait, let me catch a working version
one of the versions I coded... dunno if it works how I want it to work, but
produces the error...
--
#!/usr/bin/perl
use strict;
use warnings;
use IO::Handle;
###
my $port;
my $loop;
my $start;
my $reset;
my $setdi
On Sat, 27 Oct 2001, Jan wrote:
> i just coded a little programm as an interface between a hardware interface
> on the serial port and a database, but when i use strict, perl always makes
> complaints like:
>
> Unquoted string "iface" may clash with future reserved word at
> iface2dbgeneric.pl li
11 matches
Mail list logo
