I've often thought that a separator character would be useful in regex modifier strings to improve readability. Literal numbers have the  _ (underscore) for this reason, and I don't see why this separator cannot be "overloaded" for use in regexes.

E.g., rather than
    m{ ... }xmsgco
or
    s{ ... }{...}xmsgeepo
one might write
    m{ ... }xms_gc_o
or
    s{ ... }{...}xms_geep_o
(just to fabricate some extreme cases). Of course, my own personal practice is always to use an  /xms modifier tail, so a separator would always fall after this mandatory group if there were additional modifiers.

Give a man a fish:  <%-{-{-{-<

In reply to Re: [OT - Separator character]: Best Practice: Order of regex modifiers? by AnomalousMonk
in thread Best Practice: Order of regex modifiers? by LanX

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.