On Fri, Sep 15, 2000 at 02:03:09PM -0400, Spider Boardman <spider@Orb.Nashua.NH.US> wrote: > Hmm. 50% ain't all that good. Fixing this will require that we > fix $1 et al as well. What is broken about $1 (I am not clear about the interpretation..). AFAICS, $1 is magic, and the UTF8-flag will only be set after the first get. My original bug-report about $1 was caused by pp_concat not honoring this by first looking at the flag (where it wasn't set) and then invoking magic. So the question is: who is wrong, the user (i.e. pp_concat and probably other placses) who doesn't check early enough, or the regex op who should set the utf8-flag. IMHO, delaying the flag setting (as it happens now) seems right to me. -- -----==- | ----==-- _ | ---==---(_)__ __ ____ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / pcg@opengroup.org |e| -=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | |Thread Previous | Thread Next