Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

As the others already mentioned, it is about personal taste. But maybe more: it is how the people that maintain the code prefer to read it. If you are the only one, do what you prefer best. If it is a team, please follow the guidelines of the team and be consistent in that.

I never use the func () if $expr; syntax, because that is - for my mind - exactly the wrong way around.

I also never use && and || to do so, because it then doesn't differ enough with expressions:

$expr1 && $expr2 and action (); $expr1 || $expr2 or action ();

And if it gets more complicated, go to Three. Whenever in doubt, use parens:

if ($expr1 && $expr2 or $expr3 && ($expr4 || $expr5)) { action1 (); action2 (); }

So, I never ever use Two (and in our team when we see code like that it is immediately rewritten to One or Three).

Side note: I have one colleague that just cannot cope in his mind with unless. Not all people think alike, certainly when mixed languages (peoples languages, not computer languages) are involved.

Three has the ((very) big) advantage of being able to insert new code when the condition meets without changing the rest of the code.


Enjoy, Have FUN! H.Merijn

In reply to Re: A matter of style: how to perform a simple action based on a simple condition? by Tux
in thread A matter of style: how to perform a simple action based on a simple condition? by muba

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others sharing their wisdom with the Monastery: (4)
As of 2024-04-23 07:33 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found