Pike-devel April 2008

pike-devel@lists.lysator.liu.se

7 participants
18 discussions

[Bug] Regexp() and $ (was: Re: [Bug] Regexp.PCRE("n*") multiple match endless loop)
by bertrand.lupart＠linkeo.com 16 Apr '08

16 Apr '08

Johan Sundström (Achtung Liebe!) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > > If you don't have a PCRE enabled Pike, then there should be a solution > > with Regexp(). But it seems like there's a little bug with $ on > > Regexp(), but one bug at a time :) > > Not if it is the stone age Regexp(), as that one did/does not handle > strings with null characters in it (except in cases where you really > *want* it to treat \0 as end-of-string). Interresting to know. \0 could be replaced beforehand using replace(), then Regexp() used. Even in this case, i guess we have a problem: ^ works: ----8<----8<----8<----8<---- > string bar = "oofoo"; > Regexp("^[o]+")->replace(bar, ""); (1) Result: "foo" ---->8---->8---->8---->8---- While $ seems not: ----8<----8<----8<----8<---- > Regexp("[o]+$")->replace(bar, ""); (2) Result: "f" ---->8---->8---->8---->8---- -- Bertrand LUPART http://bertrand.gotpike.org/

1 0

[Bug] Regexp.PCRE("n*") multiple match endless loop (was: Re: Regexp troubles)
by bertrand.lupart＠linkeo.com 16 Apr '08

16 Apr '08

Mirar @ Pike developers forum <10353(a)lyskom.lysator.liu.se> wrote: > >However, i'd like to know why while doing this: > >----8<----8<----8<----8<---- > >> object r = Regexp.PCRE.Studied("[\\W]*$"); > >> r->replace(foo, ""); > >---->8---->8---->8---->8---- > >Pike eats all my CPU and the command never finish. > > Good question. The PCRE code should be easy to read though, feel free > to investigate? :) When using n* (zero or more n), Regexp.PCRE._pcre()->exec() returns an array of two identical int. ----8<----8<----8<----8<---- $ pike Pike v7.6 release 112 running Hilfe v3.5 (Incremental Pike Frontend) > Regexp.PCRE._pcre("o+")->exec("foobar",0); (1) Result: ({ /* 2 elements */ 1, 3 }) > Regexp.PCRE._pcre("o*")->exec("foobar",0); (2) Result: ({ /* 2 elements */ 0, 0 }) ---->8---->8---->8---->8---- For each replace, Regexp.PCRE()->replace() attempts to execute the regular expression at the end of the previous hit. It uses the return from exec as a start and end offset. Since the start and end offset returned by exec() are the same, this results in a infinite loop. ----8<----8<----8<----8<---- $ pike Pike v7.6 release 112 running Hilfe v3.5 (Incremental Pike Frontend) > string foo = "foobar"; > Regexp.PCRE("o+")->replace(foo,""); ({ /* 2 elements */ 1, 3 }) -1 (1) Result: "fbar" > Regexp.PCRE("o*")->replace(foo,""); ({ /* 2 elements */ 0, 0 }) ({ /* 2 elements */ 0, 0 }) ({ /* 2 elements */ 0, 0 }) ({ /* 2 elements */ 0, 0 }) ... infinite loop ... ---->8---->8---->8---->8---- Please note that Regexp.PCRE()->matchall() obviously suffers from the same problem: ----8<----8<----8<----8<---- $ pike Pike v7.6 release 112 running Hilfe v3.5 (Incremental Pike Frontend) > string foo = "foobar"; > Regexp.PCRE("o+")->matchall(foo, lambda(mixed s){ werror("%O\n",s); } ); ({ /* 1 element */ "oo" }) (1) Result: Regexp.PCRE.StudiedWidestring("o+") > Regexp.PCRE("o*")->matchall(foo, lambda(mixed s){ werror("%O\n",s); } ); ({ /* 1 element */ "" }) ({ /* 1 element */ "" }) ... infinite loop ... ---->8---->8---->8---->8---- I don't know which code should be fixed for now. I don't understand the documentation for exec() when it returns an array here: <http://pike.ida.liu.se/generated/manual/modref/ex/predef_3A_3A/Regexp/P CRE/_pcre/exec.html> -- Bertrand LUPART http://bertrand.gotpike.org/

4 4

Strong type checking
by cschalkwijk 16 Apr '08

16 Apr '08

Is there a way to force strong type checking with pike (7.4)? It seems that I can pass an int to a method that requires a string and assign an int to a string variable. Coen __________________________________________________________ Deze e-mail en de inhoud is vertrouwelijk en uitsluitend bestemd voor de geadresseerde(n). Indien u niet de geadresseerde bent van deze e-mail verzoeken wij u dit direct door te geven aan de verzender door middel van een reply e-mail en de ontvangen e-mail uit uw systemen te verwijderen. Als u geen geadresseerde bent, is het niet toegestaan om kennis te nemen van de inhoud, deze te kopieren, te verspreiden, bekend te maken aan derden noch anderszins te gebruiken. The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please notify us immediately if you have received it in error by reply e-mail and then delete this message from your system. __________________________________________________________

2 1

utime
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 16 Apr '08

16 Apr '08

There is a #ifdef _UTIMBUF_DEFINED struct _utimbuf b; #else struct utimbuf b; #endif in system.c, but I don't see anything that could define _UTIMBUF_DEFINED.

4 4

Re: Regexp troubles
by bertrand.lupart＠linkeo.com 15 Apr '08

15 Apr '08

1 0

Regexp troubles
by cschalkwijk 15 Apr '08

15 Apr '08

(using pike 7.4 r464) I want to replace something at the end of a string, but I can't get it done: I don't know the exact contents of the string when executing code, mind you. string test = "aaa123aaa"; Regex re = Regex("[a]$"); string result = re->replace(test,""); results in: "123b" while I want it to be 'aaa123'. using "^[a]" results in "123aaa". What am I doing wrong? Eventually I want to convert a string like " This is some text \0\0\0" to " This is some text". Greets, Coen __________________________________________________________ Deze e-mail en de inhoud is vertrouwelijk en uitsluitend bestemd voor de geadresseerde(n). Indien u niet de geadresseerde bent van deze e-mail verzoeken wij u dit direct door te geven aan de verzender door middel van een reply e-mail en de ontvangen e-mail uit uw systemen te verwijderen. Als u geen geadresseerde bent, is het niet toegestaan om kennis te nemen van de inhoud, deze te kopieren, te verspreiden, bekend te maken aan derden noch anderszins te gebruiken. The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please notify us immediately if you have received it in error by reply e-mail and then delete this message from your system. __________________________________________________________

4 3

pike-cms?
by Martin B�hr 14 Apr '08

14 Apr '08

hi, anyone noticed this yet? http://code.google.com/p/pike-cms/ might be good to tell those guys that their name and the use of the pike tag is very missleading. greetings, martin.

2 2

pikefarm and code librarian no longer seeing updates from cvs?
by Martin Bähr 08 Apr '08

08 Apr '08

hi, code librarian and pikefarm are not picking up any changes from cvs since this morning. any ideas what could be the issue? greetings, martin.

4 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pike-devel April 2008