LibRegex: Add a regular expression library
This commit is a mix of several commits, squashed into one because the
commits before 'Move regex to own Library and fix all the broken stuff'
were not fixable in any elegant way.
The commits are listed below for "historical" purposes:
- AK: Add options/flags and Errors for regular expressions
Flags can be provided for any possible flavour by adding a new scoped enum.
Handling of flags is done by templated Options class and the overloaded
'|' and '&' operators.
- AK: Add Lexer for regular expressions
The lexer parses the input and extracts tokens needed to parse a regular
expression.
- AK: Add regex Parser and PosixExtendedParser
This patchset adds a abstract parser class that can be derived to implement
different parsers. A parser produces bytecode to be executed within the
regex matcher.
- AK: Add regex matcher
This patchset adds an regex matcher based on the principles of the T-REX VM.
The bytecode pruduced by the respective Parser is put into the matcher and
the VM will recursively execute the bytecode according to the available OpCodes.
Possible improvement: the recursion could be replaced by multi threading capabilities.
To match a Regular expression, e.g. for the Posix standard regular expression matcher
use the following API:
```
Pattern<PosixExtendedParser> pattern("^.*$");
auto result = pattern.match("Well, hello friends!\nHello World!"); // Match whole needle
EXPECT(result.count == 1);
EXPECT(result.matches.at(0).view.starts_with("Well"));
EXPECT(result.matches.at(0).view.end() == "!");
result = pattern.match("Well, hello friends!\nHello World!", PosixFlags::Multiline); // Match line by line
EXPECT(result.count == 2);
EXPECT(result.matches.at(0).view == "Well, hello friends!");
EXPECT(result.matches.at(1).view == "Hello World!");
EXPECT(pattern.has_match("Well,....")); // Just check if match without a result, which saves some resources.
```
- AK: Rework regex to work with opcodes objects
This patchsets reworks the matcher to work on a more structured base.
For that an abstract OpCode class and derived classes for the specific
OpCodes have been added. The respective opcode logic is contained in
each respective execute() method.
- AK: Add benchmark for regex
- AK: Some optimization in regex for runtime and memory
- LibRegex: Move regex to own Library and fix all the broken stuff
Now regex works again and grep utility is also in place for testing.
This commit also fixes the use of regex.h in C by making `regex_t`
an opaque (-ish) type, which makes its behaviour consistent between
C and C++ compilers.
Previously, <regex.h> would've blown C compilers up, and even if it
didn't, would've caused a leak in C code, and not in C++ code (due to
the existence of `OwnPtr` inside the struct).
To make this whole ordeal easier to deal with (for now), this pulls the
definitions of `reg*()` into LibRegex.
pros:
- The circular dependency between LibC and LibRegex is broken
- Eaiser to test (without accidentally pulling in the host's libc!)
cons:
- Using any of the regex.h functions will require the user to link -lregex
- The symbols will be missing from libc, which will be a big surprise
down the line (especially with shared libs).
Co-Authored-By: Ali Mohammad Pur <ali.mpfard@gmail.com>
2020-04-26 14:45:10 +02:00
|
|
|
/*
|
|
|
|
* Copyright (c) 2020, Emanuel Sprung <emanuel.sprung@gmail.com>
|
|
|
|
* All rights reserved.
|
|
|
|
*
|
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
* modification, are permitted provided that the following conditions are met:
|
|
|
|
*
|
|
|
|
* 1. Redistributions of source code must retain the above copyright notice, this
|
|
|
|
* list of conditions and the following disclaimer.
|
|
|
|
*
|
|
|
|
* 2. Redistributions in binary form must reproduce the above copyright notice,
|
|
|
|
* this list of conditions and the following disclaimer in the documentation
|
|
|
|
* and/or other materials provided with the distribution.
|
|
|
|
*
|
|
|
|
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
|
|
|
|
* AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
|
|
|
|
* DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
|
|
|
|
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
|
|
|
|
* SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
|
|
|
|
* CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
|
|
|
|
* OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
|
|
|
|
* OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#pragma once
|
|
|
|
|
|
|
|
#include <AK/Forward.h>
|
|
|
|
#include <AK/StringView.h>
|
|
|
|
|
|
|
|
namespace regex {
|
|
|
|
|
|
|
|
#define ENUMERATE_REGEX_TOKENS \
|
|
|
|
__ENUMERATE_REGEX_TOKEN(Eof) \
|
|
|
|
__ENUMERATE_REGEX_TOKEN(Char) \
|
|
|
|
__ENUMERATE_REGEX_TOKEN(Circumflex) \
|
|
|
|
__ENUMERATE_REGEX_TOKEN(Period) \
|
|
|
|
__ENUMERATE_REGEX_TOKEN(LeftParen) \
|
|
|
|
__ENUMERATE_REGEX_TOKEN(RightParen) \
|
|
|
|
__ENUMERATE_REGEX_TOKEN(LeftCurly) \
|
|
|
|
__ENUMERATE_REGEX_TOKEN(RightCurly) \
|
|
|
|
__ENUMERATE_REGEX_TOKEN(LeftBracket) \
|
|
|
|
__ENUMERATE_REGEX_TOKEN(RightBracket) \
|
|
|
|
__ENUMERATE_REGEX_TOKEN(Asterisk) \
|
|
|
|
__ENUMERATE_REGEX_TOKEN(EscapeSequence) \
|
|
|
|
__ENUMERATE_REGEX_TOKEN(Dollar) \
|
|
|
|
__ENUMERATE_REGEX_TOKEN(Pipe) \
|
|
|
|
__ENUMERATE_REGEX_TOKEN(Plus) \
|
|
|
|
__ENUMERATE_REGEX_TOKEN(Comma) \
|
|
|
|
__ENUMERATE_REGEX_TOKEN(Slash) \
|
|
|
|
__ENUMERATE_REGEX_TOKEN(EqualSign) \
|
|
|
|
__ENUMERATE_REGEX_TOKEN(HyphenMinus) \
|
|
|
|
__ENUMERATE_REGEX_TOKEN(Colon) \
|
|
|
|
__ENUMERATE_REGEX_TOKEN(Questionmark)
|
|
|
|
|
|
|
|
enum class TokenType {
|
|
|
|
#define __ENUMERATE_REGEX_TOKEN(x) x,
|
|
|
|
ENUMERATE_REGEX_TOKENS
|
|
|
|
#undef __ENUMERATE_REGEX_TOKEN
|
|
|
|
};
|
|
|
|
|
|
|
|
class Token {
|
|
|
|
public:
|
|
|
|
Token() = default;
|
|
|
|
Token(const TokenType type, const size_t start_position, const StringView value)
|
|
|
|
: m_type(type)
|
|
|
|
, m_position(start_position)
|
|
|
|
, m_value(value)
|
|
|
|
{
|
|
|
|
}
|
|
|
|
|
|
|
|
TokenType type() const { return m_type; }
|
|
|
|
const StringView& value() const { return m_value; }
|
|
|
|
size_t position() const { return m_position; }
|
|
|
|
|
|
|
|
const char* name() const;
|
|
|
|
static const char* name(const TokenType);
|
|
|
|
|
|
|
|
private:
|
|
|
|
TokenType m_type { TokenType::Eof };
|
|
|
|
size_t m_position { 0 };
|
|
|
|
StringView m_value { nullptr };
|
|
|
|
};
|
|
|
|
|
|
|
|
class Lexer {
|
|
|
|
public:
|
|
|
|
Lexer() = default;
|
|
|
|
explicit Lexer(const StringView source);
|
|
|
|
Token next();
|
|
|
|
void reset();
|
|
|
|
void back(size_t offset);
|
|
|
|
void set_source(const StringView source) { m_source = source; }
|
2020-11-27 19:33:53 +03:30
|
|
|
bool try_skip(char);
|
2020-11-28 12:27:59 +03:30
|
|
|
char skip();
|
2020-11-27 19:33:53 +03:30
|
|
|
|
LibRegex: Add a regular expression library
This commit is a mix of several commits, squashed into one because the
commits before 'Move regex to own Library and fix all the broken stuff'
were not fixable in any elegant way.
The commits are listed below for "historical" purposes:
- AK: Add options/flags and Errors for regular expressions
Flags can be provided for any possible flavour by adding a new scoped enum.
Handling of flags is done by templated Options class and the overloaded
'|' and '&' operators.
- AK: Add Lexer for regular expressions
The lexer parses the input and extracts tokens needed to parse a regular
expression.
- AK: Add regex Parser and PosixExtendedParser
This patchset adds a abstract parser class that can be derived to implement
different parsers. A parser produces bytecode to be executed within the
regex matcher.
- AK: Add regex matcher
This patchset adds an regex matcher based on the principles of the T-REX VM.
The bytecode pruduced by the respective Parser is put into the matcher and
the VM will recursively execute the bytecode according to the available OpCodes.
Possible improvement: the recursion could be replaced by multi threading capabilities.
To match a Regular expression, e.g. for the Posix standard regular expression matcher
use the following API:
```
Pattern<PosixExtendedParser> pattern("^.*$");
auto result = pattern.match("Well, hello friends!\nHello World!"); // Match whole needle
EXPECT(result.count == 1);
EXPECT(result.matches.at(0).view.starts_with("Well"));
EXPECT(result.matches.at(0).view.end() == "!");
result = pattern.match("Well, hello friends!\nHello World!", PosixFlags::Multiline); // Match line by line
EXPECT(result.count == 2);
EXPECT(result.matches.at(0).view == "Well, hello friends!");
EXPECT(result.matches.at(1).view == "Hello World!");
EXPECT(pattern.has_match("Well,....")); // Just check if match without a result, which saves some resources.
```
- AK: Rework regex to work with opcodes objects
This patchsets reworks the matcher to work on a more structured base.
For that an abstract OpCode class and derived classes for the specific
OpCodes have been added. The respective opcode logic is contained in
each respective execute() method.
- AK: Add benchmark for regex
- AK: Some optimization in regex for runtime and memory
- LibRegex: Move regex to own Library and fix all the broken stuff
Now regex works again and grep utility is also in place for testing.
This commit also fixes the use of regex.h in C by making `regex_t`
an opaque (-ish) type, which makes its behaviour consistent between
C and C++ compilers.
Previously, <regex.h> would've blown C compilers up, and even if it
didn't, would've caused a leak in C code, and not in C++ code (due to
the existence of `OwnPtr` inside the struct).
To make this whole ordeal easier to deal with (for now), this pulls the
definitions of `reg*()` into LibRegex.
pros:
- The circular dependency between LibC and LibRegex is broken
- Eaiser to test (without accidentally pulling in the host's libc!)
cons:
- Using any of the regex.h functions will require the user to link -lregex
- The symbols will be missing from libc, which will be a big surprise
down the line (especially with shared libs).
Co-Authored-By: Ali Mohammad Pur <ali.mpfard@gmail.com>
2020-04-26 14:45:10 +02:00
|
|
|
private:
|
|
|
|
ALWAYS_INLINE char peek(size_t offset = 0) const;
|
|
|
|
ALWAYS_INLINE void consume();
|
|
|
|
|
|
|
|
StringView m_source {};
|
|
|
|
size_t m_position { 0 };
|
|
|
|
size_t m_previous_position { 0 };
|
|
|
|
Token m_current_token { TokenType::Eof, 0, StringView(nullptr) };
|
|
|
|
int m_current_char { 0 };
|
|
|
|
};
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
using regex::Lexer;
|