Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much
 
PerlMonks  

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

I hate style arguments. Look, we have perltidy. Any 'style' elements you don't like can probably be "corrected" by your .perltidyrc. If they can't, then as long as they don't make the code unintelligable -- and I mean truly unintelligable -- who cares? Adapt, already.

It's called "style" for a reason. Like styles of dress or decorating, coding style is largely an individual choice. Now, in corporate environments there are style standards, just like there are style standards in the form of dress codes. And, some very basic things can be applied to any public code -- after all, you can't walk around naked most places, there are minimum standards.

Beyond those "environmental minumums", though, if you're a big burly guy with a perpetual 5-o'clock shadow who prefers to wear a pink tu-tu -- what should I care? One of my cow-orkers insists on Hungarian notation (in Perl). I don't get it, but it helps him and doesn't significantly hurt me: all I ask is that he not get his undies in a bunch if I forget.

Having arguments about which style is "better" is largely like arguing the finer points of wearing pink tu-tu's. One might make the argument that a pink tu-tu makes just about anyone look silly; but what if someone wants to look silly? What if someone wants to use unless <cond> <action>? What does it really matter?

To be clear, I'm not talking about mistakes that are sometimes classified as style and have measurable changes. For example, using C-style for loops needlessly (easily causes bugs) or using open FH, "<$var"; (security risk). I'm talking about true "style" arguments.

Sure, suggest "hey, I see you had this problem -- here's a style tip for you". Hell, I'd suggest to a portly friend that horizontal stripes are probably not the best idea (I know this from experience, btw). But I wouldn't hit him over the head with it if he wanted to wear them anyway.

<-radiant.matrix->
Larry Wall is Yoda: there is no try{} (ok, except in Perl6; way to ruin a joke, Larry! ;P)
The Code that can be seen is not the true Code
"In any sufficiently large group of people, most are idiots" - Kaa's Law

In reply to Re: Commonly accepted style guide? by radiantmatrix
in thread Commonly accepted style guide? by dragonchild

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



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    [Corion]: ambrus: Yeah, I read that, but it's somewhat vague as in what I really have to implement, and where/how my "other" mainloop should/needs to call AnyEvent
    [Corion]: (or maybe I just work better from existing code that I munge until it works and I understand it rather than a short abstract text like "implement everything that's needed" ;) )
    [ambrus]: Corion: I think in this case you can get away with only a stub for idle, one that always dies when you create it, because AnyEvent::HTTP doesn't use it, not even indirectly through AnyEvent::Handle or AnyEvent::Socket or AnyEvent::DNS.
    [Corion]: The "and I understand it" part is optional.
    [Corion]: ambrus: Yes but I also need to implement the file / IO watcher, because Prima has that (in Prima::File), and I need to supply the appropriate thing to make push_write etc. work with Prima
    [ambrus]: Corion: yes, you need to implement the io watcher, which should be simple because Prima::File is basically that, and the timer watcher form Prima::Timer
    [Corion]: ... or so I think. As I said, I'm somewhat vague on how to make AnyEvent cooperate with a callback-driven IO event loop that gives me callbacks when data is available or can be written

    How do I use this? | Other CB clients
    Other Users?
    Others cooling their heels in the Monastery: (9)
    As of 2016-12-08 12:15 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?
      On a regular basis, I'm most likely to spy upon:













      Results (141 votes). Check out past polls.