text_combined: demerphq oryiufjngmailcom 101607 pagaltzis wrote tels 20071015 1735 wonder substra01 slower superificially informed guess substr construct lvalue every invocation ah make sense assuming correct would appear yet created situation everybody pays expensive price relatively speaking rarely used ooh neat feature doesnt really allow us anything couldnt ok fine couldnt pass around lvalue substrings urm cares regex match performs test pattern trivial turns simple string test returning true false pattern biggest cost compiling regex paid compile time im reasonably well aware occurs order one matches executed non trivial amount code substr bogged lvalue stuff whatever fault isnt blazing faster regex serious disappointment anchored simple pattern actually never hits would call regex engine proper regtryregmatch instead goes optimiser alone still involves considerable amount bookkeeping overhead two three c subroutine calls big chunks branches whereas substr much simpler deal let happen imo says something wrong deal new features assessing cost benefits think ive guilty times regex engine general policy change introduced performance penalty worth required correctness fixed bug design error lvalue substrings really responsible would say advantage hindsight new keyword added instead making substrs everywhere slow dying death thousand cuts sigh yves perl mredebug e justanotherperlhacker wed 06 aug 2008 154100 0200 pathtools beta testing