search for: regex_t

Here are a couple of patches against the CVS (Jan 22 18:41 PST) Some C++ comments found their way into ssh.h The no64.patch puts ifdefs around buffer_get_int64() now in bufaux.[c,h] -- Tim Rice Multitalents (707) 887-1469 tim at multitalents.net -------------- next part -------------- --- ssh.h.old Mon Jan 22 18:40:58 2001 +++ ssh.h Mon Jan 22 19:02:02 2001 @@ -25,8 +25,10 @@ # include

...te that *compiled will be an > - allocated value, and must be freed with regfree(), then free(), see > - regex(3). As a special case, if regex==NULL, then set > - *compiled=NULL (regular expression NULL is intended to match > - anything). */ > -static inline int compile_regex(regex_t **compiled, char *regex, int cflags) > + * store the compiled regular expression (or NULL) in *compiled, and > + * return 0. On error with errno set, return -1. If the supplied > + * regular expression is unparseable, return -2 (an error message can > + * then be retrieved with regerror...

...for R-2-13-branch (a similar fix works for trunk as well). Jeff $ svn diff main/grep.c Index: main/grep.c =================================================================== --- main/grep.c (revision 57110) +++ main/grep.c (working copy) @@ -723,7 +723,7 @@ { SEXP pat, text, ind, ans; regex_t reg; - int i, j, n, nmatches = 0, ov, rc; + int i, j, n, nmatches = 0, ov[3], rc; int igcase_opt, value_opt, perl_opt, fixed_opt, useBytes, invert; const char *spat = NULL; pcre *re_pcre = NULL /* -Wall */; @@ -882,7 +882,7 @@ if (fixed_opt) LOGICAL(ind)[i] = fgrep_one...

...warning: passing arg 4 of `cli_getattrE' from incompatible pointer type Compiling client/clitar.c client/clitar.c:91: syntax error before `*' client/clitar.c:91: warning: data definition has no type or storage class client/clitar.c: In function `tar_parseargs': client/clitar.c:1754: `regex_t' undeclared (first use in this function) client/clitar.c:1754: (Each undeclared identifier is reported only once client/clitar.c:1754: for each function it appears in.) client/clitar.c:1754: syntax error before `)' client/clitar.c:1760: `errcode' undeclared (first use in this function)...

...h-winbind --with-ads --with-ldap --with-krb5 AIX 5.2: Compiling client/clitar.c client/clitar.c:91: error: parse error before '*' token client/clitar.c:91: warning: data definition has no type or storage class client/clitar.c: In function `tar_parseargs': client/clitar.c:1754: error: `regex_t' undeclared (first use in this function) client/clitar.c:1754: error: (Each undeclared identifier is reported only once client/clitar.c:1754: error: for each function it appears in.) client/clitar.c:1754: error: parse error before ')' token client/clitar.c:1760: error: `errcode' und...

...virt now has virStringSplit(). Tested on Fedora 18, with its use of xen 4.2. ACK; let''s get this pushed. > @@ -62,7 +64,6 @@ struct guest_arch { > static const char *xen_cap_re = "(xen|hvm)-[[:digit:]]+\\.[[:digit:]]+-(x86_32|x86_64|ia64|powerpc64)(p|be)?"; > static regex_t xen_cap_rec; > > - > static int > libxlNextFreeVncPort(libxlDriverPrivatePtr driver, int startPort) > { This looks like a spurious whitespace change in isolation, but as long as the overall file is consistent on one vs. two blank lines before functions, I don''t care if...

...in and simple: .*\.txt$ The second format was to support some search options: /.*\.txt$/i This allows for case insensitive (//i) matching and extended (//e) matching. The implementation is optimized so that it does not compile the regular expression patterns more than once, for this reasons, a regex_t* pointer was added to exclude_struct. The man pages has been updated with the new format and a few examples. -- Paul N. Faure BEng 613.266.3286 Carleton University Systems Eng paul-at-faure-dot-ca Chief Technical Officer, CertainKey Inc. paul-at-certainkey-dot-com ----...

...ould have matched the RE "regline" defined as > > tre_regcomp(&regline, "^[^:]+:[[:blank:]]*", REG_EXTENDED); > ...and used here: > if(tre_regexecb(&regline, line, 1, regmatch, 0) == 0) { > > but apparently does not. int tre_regcomp(regex_t *preg, const char *regex, int cflags) { return tre_regncomp(preg, regex, regex ? strlen(regex) : 0, cflags); } The code is a bit too 'string busy' for me to be comfortable - so I took a different approach to look for potential differences in how 32-bit versus 64-bit were viewing thing...

...ed on getting it to work. Also the OpenBSD implementation has some extensions (see docs/regex.7), if they are useful those can be added to the Regex class also. A summary of changes from OpenBSD version: - rename functions and types to avoid clashes with system one: regcomp->llvm_regcomp, ..., regex_t -> llvm_regex_t, regoff_t -> llvm_regoff_t, BAD -> REGEX_BAD ... - include strlcpy.c (llvm_strlcpy), a configure check could be added to use system's one, but the function is so simple I just unconditionally always use it - memcpy -> memmove (parameters may overlap, BSD memcpy all...

...l/lib -Wl,-rpath -Wl,/usr/local/lib -Wl,-rpath,/usr/lib Compiling client/clitar.c client/clitar.c:91: error: parse error before '*' token client/clitar.c:91: warning: data definition has no type or storage class client/clitar.c: In function `tar_parseargs': client/clitar.c:1754: error: `regex_t' undeclared (first use in this function) client/clitar.c:1754: error: (Each undeclared identifier is reported only once client/clitar.c:1754: error: for each function it appears in.) client/clitar.c:1754: error: parse error before ')' token client/clitar.c:1760: error: `errcode' und...

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

Hello, I have a question about postfix. I have a few webservers, each with their own mailing system. Obviously manually adding items can be quite tedious going from one to another to another. I am in the process of making a list of domains (commercial spammers) that bother me. My idea is to use the access file to reject them. My question is this... Can I make a text page on one of my html

Am I wrong saying that actually anyone that use klibc has to use insmod patch or build a monolithic kernel? Could not the insmod patch be include? That will make everyone life easier on klibc upgrade. Gilles

Hello, ctags(1) uses external application sort(1) for sorting the tags file. It calls it via system(3) function. Look at the /usr/src/usr.bin/ctags/ctags.c file, there are such lines here: if (uflag) { (void)asprintf(&cmd, "sort -o %s %s", outfile, outfile); if (cmd == NULL) err(1, "out of space"); system(cmd); free(cmd); cmd = NULL; } This code will be

Is there a way with the command (1.4.42) for sip show peers to see the FULL "Name/Username" field??? I have long names and mine are being truncated. Thanks Jerry

...of `cli_getattrE' from incompatible pointer type Compiling client/clitar.c client/clitar.c:91: error: parse error before '*' token client/clitar.c:91: warning: data definition has no type or storage class client/clitar.c: In function `tar_parseargs': client/clitar.c:1754: error: `regex_t' undeclared (first use in this function) client/clitar.c:1754: error: (Each undeclared identifier is reported only once client/clitar.c:1754: error: for each function it appears in.) client/clitar.c:1754: error: parse error before ')' token client/clitar.c:1760: error: `errcode' u...

...ern study error\n\t'%s'\n"), errorptr); @@ -482,7 +486,11 @@ } vmaxset(vmax2); } +#ifdef PCRE_CONFIG_JIT + pcre_free_study(re_pe); +#else pcre_free(re_pe); +#endif pcre_free(re_pcre); } else if (!useBytes && use_UTF8) { /* ERE in wchar_t */ regex_t reg; @@ -867,12 +875,12 @@ warning(_("PCRE pattern compilation error\n\t'%s'\n\tat '%s'\n"), errorptr, spat+erroffset); error(_("invalid regular expression '%s'"), spat); - if (n > 10) { - re_pe = pcre_study(re_pcre, 0, &errorptr)...

...ter.c (working copy) @@ -357,7 +357,7 @@ int i, j, len, tlen, ntok, slen; int extended_opt, cflags, fixed_opt, perl_opt; char *pt = NULL; - const char *buf, *split = "", *bufp, *laststart; + const char *buf, *split = "", *bufp, *laststart, *ebuf = NULL; regex_t reg; regmatch_t regmatch[1]; pcre *re_pcre = NULL; @@ -419,7 +419,8 @@ if(fixed_opt) { /* This is UTF-8 safe since it compares whole strings */ laststart = buf; - for(bufp = buf; bufp - buf < strlen(buf); bufp++) { + ebuf = buf + strlen(buf); + for(bufp = buf; bufp <...

On 2015-12-17 19:30, peter dalgaard wrote: > Presumably the file in question is one of > > Peter-Dalgaards-MacBook-Air:BUILD pd$ grep -r "^Package: tools" * > library/tools/DESCRIPTION:Package: tools > src/library/tools/DESCRIPTION:Package: tools > > so the first thing I'd do is to have a good look at those files and see if they got somehow corrupted. > >

...allVectorImpl<StringRef> *Matches, bool AllowBeginOfLine = true, bool AllowEndOfLine = true); > + bool match_sub(const char *string, llvm_regmatch_t pmatch[], > + unsigned nmatch, bool notbol=false, bool noteol=false); > + private: > + llvm_regex_t preg; > + }; > +} > diff --git a/include/llvm/Support/regex.h b/include/llvm/Support/regex.h This won't work on Windows as stands (Regex.h == regex.h), but I think we should just keep regex.h private which solves the problem (still nice to rename it to avoid confusion, llvm_regex.h...