in reply to Best Practice: Order of regex modifiers?

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:  <%-{-{-{-<

Replies are listed 'Best First'.
Re^2: [OT - Separator character]: Best Practice: Order of regex modifiers?
by LanX (Saint) on Feb 01, 2017 at 18:29 UTC
      ... the use of o seems to be discouraged.

      I only latched onto  /o because I was casting about for something to use in a manufactured example.

      AFAIU, the  /o modifier is only useful now in those very limited cases in which one wishes to prevent recompilation of a  qr// m// s/// even when interpolated Regexp objects or strings have changed. My understanding is that these operators will not now recompile on each execution unless an interpolated regex/string has changed.


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

        AFAIU, the /o modifier is only useful now

        Hi, check the link, /o has been useless since about 5.6, the docs really ought to read o - pretend to optimize your code, but actually introduce bugs and perl ought to reject /o outright :)

        Also, there is no way this thread is off topic, thats some serious lack of caffeine