doubling the number of 'quoting' characters…("x" vs. qq{x})

In the realm of your discussion it's (\"x\" vs. qq{x}) which makes the score even.

I don't think it would catch on as a routine practice.

It is routine practise, but that may be only me. For one I don't like "external" characters inside my perl code (the backslash belonging to the cmd.exe, and is not seen by perl), and secondly it's actually easier to parse when read (for my brain at least).

It is not only you, pKai. I also routinely make a practice of using some alternate Perl quoting delimiters, when writing a one-liner for Windows/CMD or one that I think might ever run on Windows/CMD.

In my experience it only takes a little practice to "see" the quoted string standing out clearly when using a q<some-char> construct, just as or nearly as easily as one without practice does with ordinary "s. But then I write a lot of Perl.

Since it is tangential to this reply I won't go deeply into it, but one pet peeve of mine concerns assumptions about what shell a Win32 Perler is using. There are UNIX sh -like shells being used on MS Windows. There's a special environmental variable, PERL5SHELL, addressing that. Yet most all of the core Perl utility code (i.e. for things like ExtUtils) assumes that a command interpreter on Windows has to be the CMD.exe or command.com type. I feel a bit mistreated ;-). The 3 people still using MINT systems get support, but I as part of who knows how many hundreds or thousands using a 3rd-party UNIX-like shell on MS Windows cannot? By what logic exactly? Because there's so few of us? Only in relation to the total user base for MS Windows. So 3 MINT users or 48 FooIX-1.0 users get support, but trying to use MS Windows better gets us punishment? ;-)

Yumpy, you'll find some more MS Windows / Perl portability notes (especially relating to the creation of DOSKEY macros to fill the role that BASH functions do, in the CMD shell), on my home node. Down past the "meta" stuff relating to my experience in 6 years here at Perlmonks. Ignore the growling and squeals of moral distress if that's not what you're into. ;-)

    Soren A / somian / perlspinr / Intrepid 

--
Words can be slippery, so consider who speaks as well as what is said; know as much as you can about the total context of the speaker's participation in a forum over time, before deciding that you fully comprehend the intention behind those words. If in doubt, ask for clarification before you 'flame'.

In reply to Re^4: RFC: A Primer on Writing Portable Perl Programs by Intrepid
in thread RFC: A Primer on Writing Portable Perl Programs by yumpy

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, details, 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, summary, 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.