Re: Cfengine Help: Re: Cfengine Help: cfengine 3.1.5 pcre question

2011-05-13 Thread Daniel V. Klein
There are a couple of slightly different ways of doing this in PCRE: 1) '.*(?i)cfengine.*' 2) '.*(?i:cfengine).*' The first one turns on the "/i switch for everything after it, so the .* is also case-ignored The second one turns on the "/i switch" only for "cfengine". There's no difference in

Re: Cfengine Help: Re: Cfengine Help: cfengine 3.1.5 pcre question

2011-05-13 Thread Jesse Becker
On Fri, May 13, 2011 at 08:32:05AM -0400, Mikhail Gusarov wrote: >On 05/06/2011 04:33 PM, no-re...@cfengine.com wrote: > >> BTW, I think the fact that a "." now matches ANY character rather than any >> character except a newline needs to described in the reference manual. > >I have clarified this

Re: Cfengine Help: Re: Cfengine Help: cfengine 3.1.5 pcre question

2011-05-13 Thread Mikhail Gusarov
On 05/06/2011 04:33 PM, no-re...@cfengine.com wrote: > BTW, I think the fact that a "." now matches ANY character rather than any > character except a newline needs to described in the reference manual. I have clarified this in reference manual, and updated example and comment for readtcp functi

Re: Cfengine Help: Re: Cfengine Help: cfengine 3.1.5 pcre question

2011-05-13 Thread Mikhail Gusarov
On 05/13/2011 02:19 PM, Mikhail Gusarov wrote: >> When matching multi-line responses, not that regular expressions do >> not cross newline boundaries. > > It's a bit different context -- it means that in readdtcp every line is > matched separately. Oh, wait, I am wrong -- this comment is related

Re: Cfengine Help: Re: Cfengine Help: cfengine 3.1.5 pcre question

2011-05-13 Thread Mikhail Gusarov
On 05/07/2011 11:20 PM, Aleksey Tsalolikhin wrote: > Aye. The reference manual currently states: > > When matching multi-line responses, not that regular expressions do > not cross newline boundaries. It's a bit different context -- it means that in readdtcp every line is matched separately. N

Cfengine Help: Re: Cfengine Help: Re: Cfengine Help: cfengine 3.1.5 pcre question

2011-05-08 Thread no-reply
Forum: Cfengine Help Subject: Re: Cfengine Help: Re: Cfengine Help: cfengine 3.1.5 pcre question Author: Beto Link to topic: https://cfengine.com/forum/read.php?3,21785,21836#msg-21836 Aleksey Tsalolikhin Wrote: --- > Aye. The reference man

Re: Cfengine Help: Re: Cfengine Help: cfengine 3.1.5 pcre question

2011-05-07 Thread Aleksey Tsalolikhin
On Fri, May 6, 2011 at 7:33 AM, wrote: > Forum: Cfengine Help > Subject: Re: Cfengine Help: cfengine 3.1.5 pcre question > Author: Beto > Link to topic: https://cfengine.com/forum/read.php?3,21785,21787#msg-21787 > > BTW, I think the fact that a "." now matches A

Cfengine Help: Re: Cfengine Help: cfengine 3.1.5 pcre question

2011-05-06 Thread no-reply
Forum: Cfengine Help Subject: Re: Cfengine Help: cfengine 3.1.5 pcre question Author: Beto Link to topic: https://cfengine.com/forum/read.php?3,21785,21787#msg-21787 BTW, I think the fact that a "." now matches ANY character rather than any character except a newline needs to descri

Cfengine Help: Re: Cfengine Help: cfengine 3.1.5 pcre question

2011-05-06 Thread no-reply
Forum: Cfengine Help Subject: Re: Cfengine Help: cfengine 3.1.5 pcre question Author: Beto Link to topic: https://cfengine.com/forum/read.php?3,21785,21786#msg-21786 Ahhh... Thank you Mikhail. I was starting to think I had forgotten what little I know about PCREs :) It would probably be a

Re: Cfengine Help: cfengine 3.1.5 pcre question

2011-05-06 Thread Mikhail Gusarov
On 05/06/2011 03:13 PM, no-re...@cfengine.com wrote: > Can anyone explain why "#.*" caused problems in 3.1.5 and why changing it to > "#[^\n]*" fixed the problems? I thought a "." represented any character > except a new line character and was the same thing as "[^\n]". I have made this change

Cfengine Help: cfengine 3.1.5 pcre question

2011-05-06 Thread no-reply
Forum: Cfengine Help Subject: cfengine 3.1.5 pcre question Author: Beto Link to topic: https://cfengine.com/forum/read.php?3,21784,21784#msg-21784 I used the expression "#.*" in the comment field of several readstringarry/readstringlist functions. Prior to 3.1.5 this always worked without probl