Re (2): Optimization for readability and speed (discussion)

However, the developers who are going to be maintaining code like this are not perl developers and feel that perl is "part of the problem" because the CGI's on the site (which I had no hand in) are misbehaving. It almost reminds me of C code, and I wanted to make sure that others were able to read it. It is readable, if not very perlful, imho.

dep.

--
Laziness, Impatience, Hubris, and Generosity.

Comment on Re (2): Optimization for readability and speed (discussion)

Replies are listed 'Best First'.
Re: Re: Re: Optimization for readability and speed (discussion) by merlyn (Sage) on Apr 30, 2001 at 22:26 UTC
I'm again going to disagree. What you've written is neither C nor Perl, and something kinda awful in between. Perl experts will wince, and C experts will lack the Perl understanding to pick it up. Either make it native Perl, or don't write it in Perl. It's also broken as Perl. You return from the middle of the subroutine that sets `$"`, but you don't reset it! That breaks the rest of the program. Use this instead (if you must): `local $" = '';` [download] Then no matter what exit you take, the caller's value of `$"` is preserved. -- Randal L. Schwartz, Perl hacker	[reply] [d/l]

Replies are listed 'Best First'.

Re: Re: Re: Optimization for readability and speed (discussion)
by merlyn (Sage) on Apr 30, 2001 at 22:26 UTC

Either make it native Perl, or don't write it in Perl.

It's also broken as Perl. You return from the middle of the subroutine that sets $", but you don't reset it! That breaks the rest of the program. Use this instead (if you must):

local $" = '';
[download]

Then no matter what exit you take, the caller's value of $" is preserved.
-- Randal L. Schwartz, Perl hacker

[reply]
[d/l]