A code-searching tool similar to ack, but faster.
-
Updated
Jul 9, 2021 - C
#
pcre
Here are 66 public repositories matching this topic...
A Compile time PCRE (almost) compatible regular expression matcher.
-
Updated
Aug 17, 2021 - C++
The regex-centric, fast lexical analyzer generator for C++ with full Unicode support. Faster than Flex. Accepts Flex specifications. Generates reusable source code that is easy to understand. Introduces indent/dedent anchors, lazy quantifiers, functions for lex/syntax error reporting, and more. Seamlessly integrates with Bison and other parsers.
bison
flex
compiler
regex
regular-expression
fuzzy-matching
lex
pcre
lexer
lexer-generator
regex-pattern
regular-expressions
graphviz-dot
lexical-analyzer
regex-library
regex-engine
flex-regex
-
Updated
Aug 14, 2021 - C++
Library for PHP regular expression, providing high-level API.
-
Updated
Aug 8, 2021 - PHP
experimental and very fast implementation of a grep
-
Updated
Nov 13, 2020 - C++
PCRE.NET - Perl Compatible Regular Expressions for .NET
-
Updated
Aug 18, 2021 - C#
newLISP mirror repository (unofficial)
-
Updated
May 27, 2019 - C
Unix tool: Bulk Rename Utility
-
Updated
May 30, 2020 - C++
A Haskell regular expressions library that doesn't suck
-
Updated
Nov 4, 2018 - Haskell
C++ wrapper for PCRE2 Library
cpp
regex
pcre
regex-pattern
pcre2-regex
pcre2-libraries
regex-match
pcre2-options
associated-regex
options-jpcre2
jpcre2
regex-replace
-
Updated
Jun 15, 2021 - C++
OCaml bindings to PCRE (Perl Compatibility Regular Expressions)
-
Updated
Jul 22, 2021 - OCaml
Archive copy of Stan Hoeppner's Postfix PCRE bot spam killer (fqrdns.pcre)
-
Updated
Jul 28, 2017
PCRE functions for PostgreSQL
-
Updated
May 21, 2020 - C
C automata library to build, determinize, minimize, translate regexp etc
-
Updated
Mar 26, 2016 - C
Thin covers for Dyalog APL's ⎕R and ⎕S
-
Updated
Jul 6, 2020 - APL
Improve this page
Add a description, image, and links to the pcre topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the pcre topic, visit your repo's landing page and select "manage topics."
Right now, whenever Zenmap crashes, it gives the user a stack trace and asks the user to send it to the Nmap dev list. So we get a flood of emails (most of which aren't even allowed through moderation) which often contain just a stack trace with no subject line or any explanatory text in the message body. Lots of these are for well known issues in older versions of Zenmap. So it's not very usef