search for: regex

...tory `/home/cuser/AMD_BENCH/R-2.1.1/src/main' /usr/pgi/linux86-64/6.0/bin/pgcc -I../../src/extra/zlib -I../../src/extra/bzip2 -I../../src/extra/pcre -I. -I../../src/include -I../../src/include -I/usr/pgi/linux86-64/6.0/include -I/usr/pgi/linux86-64/6.0/include/CC -DHAVE_CONFIG_H -g -O2 -c regex.c -o regex.o PGC-W-0155-64-bit integral value truncated (/usr/include/wctype.h: 109) PGC-W-0155-64-bit integral value truncated (/usr/include/wctype.h: 110) PGC-W-0155-64-bit integral value truncated (/usr/include/wctype.h: 111) PGC-W-0155-64-bit integral value truncated (/usr/include/wctype.h...

Hi all, The following tests fail because my username (csabaraduly) contains "bar" : ******************** FAIL: LLVM :: tools/llvm-objcopy/ELF/regex.test (47099 of 50832) ******************** TEST 'LLVM :: tools/llvm-objcopy/ELF/regex.test' FAILED ******************** Script: -- : 'RUN: at line 1'; /home/csabaraduly/wk/LLVM-git/__build_release_99/bin/yaml2obj /home/csabaraduly/wk/LLVM-git/llvm/test/tools/llvm-objcopy/ELF/regex.t...

...v-bounces at lists.llvm.org] On Behalf Of Jordan Rupprecht via llvm-dev Sent: Friday, March 29, 2019 1:13 PM To: Csaba Raduly Cc: llvm-dev Subject: Re: [llvm-dev] Test failure due to file path True, it could probably skip the filename printed at the beginning of readobj with something like this: #REGEX1: Symbols [#REGEX1-NOT: foobaz #REGEX1-NOT: bar #REGEX1-NOT: rebar Mind contributing a patch? :) On Fri, Mar 29, 2019 at 9:53 AM Csaba Raduly via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote: Hi all, The following tests fail because my us...

Dear all, I have made a fairly complex dialplan where I am using the REGEX function in many places. This works so far, but I wasn't able to solve the following problem. What I would like to do is the following (please note that this is normal regex syntax and obviously not what the REGEX function expects, but I hope it shows the idea): same => n(A1), GotoIf($[${...

On Aug 23, 2009, at 11:59 PM, Török Edwin wrote: > If LLVM is going to have an integrated regex library I suggest using > it > regardless if the platform has one. > The LLVM integrated regex library will provide consistent behaviour > and > execution time, the system one will not. Hi Edwin, Can you propose the openbsd implementation as a patch to lib/support? -Chris

...ere; or is the problem on my end? My installed Perl is Strawberry 5.28.0.1-64 bit. Thank you, Avi (Sent from an iPhone, so my apologies if HTML also comes through) ------ Making HTML documentation ------ creating doc/manual/version.texi creating doc/manual/R-FAQ.html Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.32), passed through in regex; marked by <-- HERE in m/^\s+@([[:alnum:]][[:alnum:]\-]*)({ <-- HERE })?\s*/ at C:/Rtools/texinfo5/Texinfo/Parser.pm line 5441. Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.32), pass...

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. > diff --git a/include/llvm/Support/Regex.h b/include/llvm/Support/Regex.h > new file mode 100644 > index 0000000..314bff4 > --- /dev/null > +++ b/include/llvm/Support/Regex.h > @@ -0,0 +1,49 @@ > +//===-- Regex.h - Regular Expression matcher implementation -------------===...

On 2009-08-24 20:14, Chris Lattner wrote: > On Aug 23, 2009, at 11:59 PM, Török Edwin wrote: >> If LLVM is going to have an integrated regex library I suggest using it >> regardless if the platform has one. >> The LLVM integrated regex library will provide consistent behaviour and >> execution time, the system one will not. > > Hi Edwin, > > Can you propose the openbsd implementation as a patch to lib/suppo...

I've Dovecot and dovecot-sieve v 2.2.27 installed on a Debian 9.6. I'm trying to set a Sieve filter which will redirect all emails from `info` (i.e. .info) TLD to another email. This is the filter: require ["regex"]; # rule:[test] if header :regex "from" "info$" { redirect "subbs at domain.com"; } It's not being honored; all emails from .info TLD ends up in the inbox and none are redirected. Let me know what I'm doing wrong. Thanks. -------------- next part ------...

...rogram supervision framework for= x86-linux. =3D=3D22324=3D=3D Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward = et al. =3D=3D22324=3D=3D For more details, rerun with: -v =3D=3D22324=3D=3D=20 =3D=3D22324=3D=3D Invalid read of size 4 =3D=3D22324=3D=3D at 0x81255AD: parse_expression (regex.c:5045) =3D=3D22324=3D=3D by 0x8125868: parse_branch (regex.c:4475) =3D=3D22324=3D=3D by 0x8125913: parse_reg_exp (regex.c:4420) =3D=3D22324=3D=3D by 0x81261B3: Rf_regcomp (regex.c:4384) =3D=3D22324=3D=3D Address 0x1C1E23A8 is 0 bytes after a block of size 32 a= lloc'd =3D=3D22324=3D=...

On Wed, 2019-02-20 at 10:18 +0100, Martin Johannes Dauser via dovecot wrote: > Hi! > > You forgot the wildcard '.*'?(=?Match zero or more instances of any > single character, except newline) > > require ["regex"]; > # rule:[test] > if header :regex "from" ".*info$" > { > ? redirect "subbs at domain.com"; > } > > With this rule, you are filtering emails from toplevel domain > '*.info' > or new domains that might occur in future (e.g ...

...ything seems to work just fine, except for mzR. Here is failed build: g++ -m64 -shared -L/usr/lib64/R/lib -Wl,-z,relro -o mzR.so cramp.o ramp_base64.o ramp.o RcppRamp.o RcppRampModule.o rnetCDF.o RcppPwiz.o RcppPwizModule.o RcppIdent.o RcppIdentModule.o ./boost/system/src/error_code.o ./boost/regex/src/posix_api.o ./boost/regex/src/fileiter.o ./boost/regex/src/regex_raw_buffer.o ./boost/regex/src/cregex.o ./boost/regex/src/regex_debug.o ./boost/regex/src/instances.o ./boost/regex/src/icu.o ./boost/regex/src/usinstances.o ./boost/regex/src/regex.o ./boost/regex/src/wide_posix_api.o ./boo...

...;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> <font face="Arial">Greetings,<br> <br> I'm running 1.2.7.1, and I'm trying to using the REGEX function in my dialplan.&nbsp; However, the Asterisk parser doesn't seem to understand what's going on.&nbsp; I'm trying to use REGEX to determine if a variable matches a standard 10 digit US/Canada number.&nbsp; To do this, I started with the following:<br> <br>...

...rtowc' ../main/libmain.a(util.o):util.c:(.text+0x3806): undefined reference to `mbrtowc' ../main/libmain.a(util.o):util.c:(.text+0x387c): undefined reference to `mbrtowc' ../main/libmain.a(util.o):util.c:(.text+0x39df): more undefined references to `mbrtowc' follow ../main/libmain.a(regex.o):regex.c:(.text+0x25b): undefined reference to `wcrtomb' ../main/libmain.a(regex.o):regex.c:(.text+0x37a): undefined reference to `mbrtowc' ../main/libmain.a(regex.o):regex.c:(.text+0x3dd): undefined reference to `wcrtomb' ../main/libmain.a(regex.o):regex.c:(.text+0xd3c): undefined re...

Hi, I found the following code on the net which should redirect all mails to another address depending on the time of day (useful for forwarding mails to work): require ["regex"]; if allof (header :regex "date" "(08|09|10|11|12|13|14|15|16|17):..:..", not header :regex "date" "(sat|sun)") { redirect "address at work>"; keep; } To check and test I simplified the regex to match all mails withi...

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. > I'd like to keep re_format.7, it describes the format of the regex as accepted by this implementation. I'll remove regex.3 since its not exposed. > >> diff --git a/include/llvm/Support/Regex.h b/include/llvm/Support/Regex.h >> new file mode 100644 >> ind...

...n about modifiers for pattern parameters. Vedant suggested such way. > CHECK-DEFINE-PATTERN: one_or_more(x): x {{+}} But I have some doubts. This should be equal to x+. This approach differs from standard one. In FileCheck I can write CHECK: {{x|y}}{{something}} This line will be equal to regex (x|y)(something). But if I use suggested approach and write same string in pattern CHECK-DEFINE-PATTERN: example: {{x|y}}{{something}}, it will be equal to (x|ysomething). As user I expected behavior as in first check. Thanks, Elena.

Hello, I noticed (due to a recent post by Martin Honnen to clp) that Element.Class uses wrong regexps for its operations. E.g., Element.Class.has() will find "classA" in "classA-foobar" I also changed the interface of .has() to the more general one used in .has_any() --- util.js.old 2005-08-21 19:18:40.000000000 +0200 +++ util.js 2005-08-21 19:31:42.000000000 +0200 @@ -...

...implies importing some >> implementation of this interface, e.g., Windows. On Linux, BSD, etc. >> we would try to use the platform version if available (and non- >> buggy). > > Don't do it. > They are ridiculous slow, and posix made some really dumb choices in > regexps. We want to use this from FileCheck, which we build at -O0 today. Also, each regex 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 tha...

There is a 2-block memory leak in the sub() (or any other regex-related function, probably) when the pattern argument involves a range expression, e.g., '[0-9]'. % R --debugger=valgrind --debugger-args=--leak-check=full --vanilla ==14519== Memcheck, a memory error detector. ==14519== Copyright (C) 2002-2006, and GNU GPL'd, by Julian Seward et al. =...