All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

Heh. Well, the functions where I'm doing this are generally short. For larger functions I'd probably be more inclined to keep the brackets.

The main problem I have with people using this style is that they don't indent or space worth a darn. That can get real confusing, real quick. That's probably another reason I've avoided it in the past.

Just because a feature can be misused - doesn't mean it should be misused (we Perl hackers know it best of all...). The "no bracket" single statement "if" is in C for a reason - and AFAIK it is considered good style to use it. With proper indentation, the problems you may run into become blazingly obvious. In 6 years of C experience, I've never had a bug resulting from this feature.

: 1. What is the possibility of this being added in the future?
In the near future, the probability is close to zero. In the distant
future, I'll be dead, and posterity can do whatever they like... :-) --lwall

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.