Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

C coding style change 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Don't bring that code my way!
    • 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.

      • Re:ICKY POO POO (Score:1)

        by spur (4197) on 2004.11.12 2:36 (#35968) Homepage
        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.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.