Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
I'm not sure about this


I read it as doublequote which is not preceded by backslash

But what about an escaped backslash \\" or two \\\\" ... ?

I'd rather try something like (Untested pseudocode)



$escaped = qr/\\./; $quoted = qr/ (['"]) # start (?: $escaped | [^\1] )* # inside \1 # end, probably \g-1 better /x;

NB: I didn't cover the case of unclosed quotes, which is unclear anyway.

Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery


tested - fails - good night! :)


see Re: solution wanted for break-on-spaces (w/specifics) for "working" example

In reply to Re^2: solution wanted for break-on-spaces (w/specifics) by LanX
in thread solution wanted for break-on-spaces (w/specifics) by perl-diddler

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.