search for: regexec

Hi, In R 3.4.0, the "Pattern Matching and Replacement" documentation that describes regexec(), gregexpr(), etc. states that the "text" argument to regexec is a character vector, "or an object which can be coerced by as.character to a character vector": regexec(pattern, text, ignore.case = FALSE, perl = FALSE, fixed = FALSE, useBytes = FALSE) x,...

On Aug 23, 2009, at 5:50 PM, OvermindDL1 wrote: > On Sun, Aug 23, 2009 at 6:32 PM, Daniel Dunbar<daniel at zuster.org> > wrote: >> This is too heavy, and we don't need the extra features, and regexec >> is well tested and much more standard. Unless there is an >> overwhelming > > 'regexec' I had never heard of, figured it was a library, turns out it > is a function call on *nix systems, yea, that is very much not usable > in any way shape or form, and is certai...

On Sun, Aug 23, 2009 at 6:32 PM, Daniel Dunbar<daniel at zuster.org> wrote: > This is too heavy, and we don't need the extra features, and regexec > is well tested and much more standard. Unless there is an overwhelming 'regexec' I had never heard of, figured it was a library, turns out it is a function call on *nix systems, yea, that is very much not usable in any way shape or form, and is certainly not a standard if it does not...

...st libraries.  They've got a regex > library, and a full-blown parser library (which I am using in my > front-end).  It's definitely heavier than POSIX, but it's portable, > well-tested, and loaded with features. This is too heavy, and we don't need the extra features, and regexec is well tested and much more standard. Unless there is an overwhelming agreement to add another option, I'd like to keep the discussion to the obvious choices. That is, I need to be convinced *not* to use #2, before I get derailed into discussing which form of #3 to take. - Daniel

...nstall just fine. make dist finishes cleanly, but make dist-check isn't. I am trying to only build the Unix target, this one is a bit vexing. The regengine.inc file is definitely in the .src directory and if I hand copy it to the .obj directory I still get the same error. llvm[2]: Compiling regexec.c for Release build /root/software/llvm-3.0.obj/_distcheckdir/llvm-3.0/lib/Support/regexec.c:82:25: error: regengine.inc: No such file or directory /root/software/llvm-3.0.obj/_distcheckdir/llvm-3.0/lib/Support/regexec.c: In function ‘llvm_regexec’: /root/software/llvm-3.0.obj/_distcheckdir/llvm-3....

Hello, I've just updated to wine 0.9 and now I get following error when running diablo2: err:module:load_builtin_dll failed to load .so lib for builtin L"dbghelp.dll": /usr/lib/wine/dbghelp.dll.so: symbol regexec, version GLIBC_2.3.4 not defined in file libc.so.6 with link time reference err:module:import_dll Loading library dbghelp.dll (which is needed by L"c:\\windows\\system32\\imagehlp.dll") failed (error c000007a). I'm running debian sarge and I do have installed libstdc++6, libc6 and...

Under RSPython and rpy, the regexec C function is returning nonsensical results leading to segmentation faults. This is happening in some situations under R 1.4.1 and (more often?) under R 1.5.0 on my Solaris 8 box. R 1.4.1 was compiled with gcc 2.95.2, and I've tried 1.5.0 with both gcc 2.95.2 and gcc 3.0.3. The error appea...

...PM, Chris Lattner<clattner at apple.com> wrote: > > On Aug 23, 2009, at 5:50 PM, OvermindDL1 wrote: > >> On Sun, Aug 23, 2009 at 6:32 PM, Daniel Dunbar<daniel at zuster.org> wrote: >>> >>> This is too heavy, and we don't need the extra features, and regexec >>> is well tested and much more standard. Unless there is an overwhelming >> >> 'regexec' I had never heard of, figured it was a library, turns out it >> is a function call on *nix systems, yea, that is very much not usable >> in any way shape or form, and...

...estcases use fixed > strings (in fact 100% of them do today!). This really is not very > performance sensitive. > > Regex engines like this are inherently more powerful but slower than > fixed-purpose matching logic. I don't see a reason not to use a > (slow!) simple regexec version. > I agree with Daniel Berlin, system's regcomp/regexec shouldn't be used. Slow can mean taking 30 minutes, or hanging indefinetely on some platforms with buggy regcomp/regexec. Some examples: https://wwws.clamav.net/bugzilla/show_bug.cgi?id=497 https://wwws.clamav.net/bugz...

Nice! This looks good to me but probably Chris or someone else should sign off on it. There were two minor warnings on Darwin: -- In file included from /Volumes/Data/Users/ddunbar/llvm/lib/Support/regexec.c:81: /Volumes/Data/Users/ddunbar/llvm/lib/Support/regengine.inc: In function 'sbackref': /Volumes/Data/Users/ddunbar/llvm/lib/Support/regengine.inc:665: warning: control reaches end of non-void function In file included from /Volumes/Data/Users/ddunbar/llvm/lib/Support/regexec.c:130: /Volu...

...will be matched once. Most testcases use fixed strings (in fact 100% of them do today!). This really is not very performance sensitive. Regex engines like this are inherently more powerful but slower than fixed-purpose matching logic. I don't see a reason not to use a (slow!) simple regexec version. I would also prefer not to have all the crazy features. Just supporting simple matching stuff is perfectly acceptable. We don't need unicode character classes, negative assertions, etc. We don't need the full power of perl regex's. >> My personal preference is...

...ld appreciate some help with: 1. Config/Alloca.h is now dead. Once configure and cmake support is removed, we can zap it. Can someone remove the cmake/autoconf stuff that pokes at Config/Alloca.h? 2. Daniel's regex email. I think the right answer is to just autodetect whether regcomp/regexec etc are available (his #2). Could someone add support to autoconf/cmake to detect whether the platform already supports these? -Chris

On 2009-08-27 09:06, Daniel Dunbar wrote: > 2009/8/25 Török Edwin <edwintorok at gmail.com>: > >> On 2009-08-25 21:18, Daniel Dunbar wrote: >> >>> Woot! Thanks a bunch Edwin! >>> >>> Some comments on the patch: >>> -- >>> I'm not sure if it makes sense to import the man pages, if we only >>> expose Regex.h.

...rns without matches would be > >> > shown as matches at position 0 with length 0. Hence either the > >> > pattern is compatible with the prototype or it isn't, it does not > depend > >> > on the text input. E.g., > >> > > >> >> regexec("^(([[:alpha:]]+)|([[:digit:]]+))$", c("Twelve", "12", > "Z280")) > >> > [[1]] > >> > [1] 1 1 1 0 > >> > attr(,"match.length") > >> > [1] 6 6 6 0 > >> > attr(,"useBytes") >...

...one may be different than the exact one used internally). PCRE could easily blow the stack in some cases, sadly. FWIW: Most people are much more familiar with perl tyle regexps, than they are familiar with posix style. That said, if you really have the urge to have a BSD'd implementation of regexec, at least choose something like http://laurikari.net/tre/ which is a linear time in size of string. I've never performance timed it myself, but Russ Cox says it is "efficient" ;) The Google impl was, at least if i remember right, made up of 3 engines: 1 that was a special case match...

...atterns in the regular expression? I thought that if the entire pattern matches then the subpatterns without matches would be shown as matches at position 0 with length 0. Hence either the pattern is compatible with the prototype or it isn't, it does not depend on the text input. E.g., > regexec("^(([[:alpha:]]+)|([[:digit:]]+))$", c("Twelve", "12", "Z280")) [[1]] [1] 1 1 1 0 attr(,"match.length") [1] 6 6 6 0 attr(,"useBytes") [1] TRUE [[2]] [1] 1 1 0 1 attr(,"match.length") [1] 2 2 0 2 attr(,"useBytes") [1] T...

...rcapture("(.)(.)(.)", c("abc", "def"), proto=list(A="")) A 1 a 2 c 3 d 4 f Bill Dunlap TIBCO Software wdunlap tibco.com On Tue, Oct 4, 2016 at 2:21 PM, Michael Lawrence <lawrence.michael at gene.com> wrote: > Hi Bill, > > This is a bug in regexec() and I will commit a fix. > > Thanks for the report, > Michael > > On Tue, Oct 4, 2016 at 1:40 PM, William Dunlap <wdunlap at tibco.com> wrote: > > I noticed a problem in the strcapture from R-devel (2016-09-27 r71386), > when > > the text contains a missing val...

...> that pokes at Config/Alloca.h? AFAIK, there is nothing specific for include/llvm/Config/alloca.h on the cmake build and it works fine after removing the file (checked on Linux x86_64). > 2. Daniel's regex email. I think the right answer is to just > autodetect whether regcomp/regexec etc are available (his #2). Could > someone add support to autoconf/cmake to detect whether the platform > already supports these? As I have no idea about what headers or functions have to need detected, after the changes are installed on the configure build I'll replicate them on t...

...include/llvm/Config/alloca.h on the > cmake build and it works fine after removing the file (checked on Linux > x86_64). Likewise, there is no autoconf magic for this. I killed it. >> 2. Daniel's regex email.  I think the right answer is to just >> autodetect whether regcomp/regexec etc are available (his #2).  Could >> someone add support to autoconf/cmake to detect whether the platform >> already supports these? > > As I have no idea about what headers or functions have to need detected, > after the changes are installed on the configure build I'll r...

...te ($set1408) Gas complains: perlio.s: Assembler messages: perlio.s:43549: Error: operation combines symbols in different segments clang: error: assembler command failed with exit code 1 (use -v to see invocation) specmake: *** [perlio.o] Error 1 specmake: *** Waiting for unfinished jobs.... regexec.c:3275:111: warning: use of logical '||' with constant operand [-Wconstant This is on the line $set1406 = ($.bss_end)-PerlIO_fd_refcnt .bss $.bss_end: .section .rodata.str1.1,"aMS", at progbits,1 $.str34: .asciz "r" .size $.str34, 2...