comment on

I wouldn't be surprised if sed was faster than Perl with trivial regexes, because all those fancy features come with complexity and are slowing the engine down.

But one off those features is Trie optimization° of "or" alternations with |

Hence a one-pass solution with a hash lookup like demonstrated by Anomalous could be far faster in Perl than in Sed (does Sed even allow hash lookups?)

But this also depends on details only you know, like if you expect a snippet to be processed multiple times.

Like "hidings > hiding > hide" ² wouldn't be possible with this one-pass approach, you'd need to repeat it till it doesn't replace anymore.

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery}

updates

°) see how-does-perls-regex-implementation-makes-use-of-tries#57484188

²) i.e. multiple reductions gerund after plural

In reply to Re: Need to speed up many regex substitutions and somehow make them a here-doc list by LanX
in thread Need to speed up many regex substitutions and somehow make them a here-doc list by xnous

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.


Pathologically Eclectic Rubbish Lister
	PerlMonks