Re: Dr. Watson paid my perl script a visit. . .

It might be helpful to know a little bit more about what values you have in those variables. Assuming that they're just string values, there should be no problem. I tested the exact syntax you used on my Winnt4 system with ActiveState build 628 (perl 5.6.1) and had no problems.

Upon the face of it, it seems that the problem might be in having two . operators in the same statement. Does Dr. Watson catch you when you do this in other places? Sorry I can't be of more help.

Comment on Re: Dr. Watson paid my perl script a visit. . .

Replies are listed 'Best First'.
Re: Re: Dr. Watson paid my perl script a visit. . . by MrCromeDome (Deacon) on Oct 04, 2001 at 17:52 UTC
You're absolutely correct - the variables are just holding strings. I was beginning to wonder the same thing about having multiple . operators in the same statement, so I checked out my script a little more. There are places where I have multiple concatenation operators, but those statements consist of all variables, such as: `$script = $select . $from . $where . $order_by;` [download] Maybe it has something to do with multiple concatenations involving both literals and variables? Not altogether sure. Could be worth investigating on a *NIX platform (to make sure it's not ActivePerl specific). Thanks! MrCromeDome	[reply] [d/l]

Replies are listed 'Best First'.

Re: Re: Dr. Watson paid my perl script a visit. . .
by MrCromeDome (Deacon) on Oct 04, 2001 at 17:52 UTC

I was beginning to wonder the same thing about having multiple . operators in the same statement, so I checked out my script a little more. There are places where I have multiple concatenation operators, but those statements consist of all variables, such as:

$script = $select . $from . $where . $order_by;
[download]

Thanks! MrCromeDome

[reply]
[d/l]