demerphq oryiufjngmailcom nov 11 2007 458 pm rick delaney wrote nov 10 2007 sean orourke wrote checked changing regexecc2119 flags rexec_copy_str svreadonlysv fixes dont know implications might like principle disabling copy semantics target string readonly actually good idea feel bit dopey overlooking suspect need number places logic added code involved several routines actually several files even guess would safe enough think would better put svreadonly rexec_copy_str set pp_hotc1293 xxx comment global get safe 1 vars match aware leads dramatic slowdowns g matches large strings far solution problem appears quite tricky test unsafe vars todo global rxnparens svtemptarg pl_sawampersand rxextflags rxf_eval_seenrxf_pmf_keepcopy r_flags rexec_copy_str confused slowdown first place doesnt comment global code imply rexec_copy_str set g match expressions evaluating true block scalar context matches think block list context matches id look closer dont easy source access im japan list context matches single copy target string made first match subsequent matches reusing copy scalar context matches global prevents copy however disabled check older versions blead serious performance problems g matches backed penalty pointed regard marvins point think problem dont store utf8 offset regex related match magic actually point raised mark gpw havent tuits work would nice would could store character byte offset string instead character offset would mean could avoid using utf8 scanning resolving capture buffers issue one reasons hate utf8unicode think utf32 sane way deal unicode anybody wants hack issues id would happy support efforts wont time time utf8 offset stuff definitely todo list tho id happy see someone else sort cheers yves perl mredebug e justanotherperlhacker thu 07 aug 2008 223300 0100 possible avoid slowdown large mg