| commit | f338d1e7587dfe3790f45a096574de2b4718e9d9 | [log] [tgz] |
|---|---|---|
| author | David Neto <dneto@google.com> | Mon May 08 11:06:52 2017 -0400 |
| committer | David Neto <dneto@google.com> | Mon May 08 11:06:52 2017 -0400 |
| tree | f752f80c0fe4461b85157922c62a772f36fcb7b7 | |
| parent | b6fcdac5df64580cf035048a9c4ec0a422a48a2e [diff] |
Update tests for gcc failure to parse raw strings
Effcee is a C++ library for stateful pattern matching of strings, inspired by LLVM's FileCheck command.
Effcee:
The following is from examples/main.cc:
#include <iostream> #include <sstream> #include "effcee/effcee.h" // Checks standard input against the list of checks provided as command line // arguments. // // Example: // cat <<EOF >sample_data.txt // Bees // Make // Delicious Honey // EOF // effcee-example <sample_data.txt "CHECK: Bees" "CHECK-NOT:Sting" "CHECK: Honey" int main(int argc, char* argv[]) { // Read the command arguments as a list of check rules. std::ostringstream checks_stream; for (int i = 1; i < argc; ++i) { checks_stream << argv[i] << "\n"; } // Read stdin as the input to match. std::stringstream input_stream; std::cin >> input_stream.rdbuf(); // Attempt to match. The input and checks arguments can be provided as // std::string or pointer to char. auto result = effcee::Match(input_stream.str(), checks_stream.str(), effcee::Options().SetChecksName("checks")); // Successful match result converts to true. if (result) { std::cout << "The input matched your check list!" << std::endl; } else { // Otherwise, you can get a status code and a detailed message. switch (result.status()) { case effcee::Result::Status::NoRules: std::cout << "error: Expected check rules as command line arguments\n"; break; case effcee::Result::Status::Fail: std::cout << "The input failed to match your check rules:\n"; break; default: break; } std::cout << result.message() << std::endl; return 1; } return 0; }
For more examples, see the matching tests in effcee/match_test.cc.
Effcee is a work in progress.
What works:
What is left to do:
%% appears where a regular expression is expected, then it expands to the regular expression for a local identifier in LLVM assembly language, i.e. %[-a-zA-Z$._][-a-zA-Z$._0-9]*. This enables you to write precise tests with less fuss.What is left to do, but lower priority:
Effcee is licensed under terms of the Apache 2.0 license. If you are interested in contributing to this project, please see CONTRIBUTING.md.
This is not an official Google product (experimental or otherwise), it is just code that happens to be owned by Google. That may change if Effcee gains contributions from others. See the CONTRIBUTING.md file for more information. See also the AUTHORS and CONTRIBUTORS files.
effcee/ : library source code, and teststhird_party/: third party open source packages, downloaded separatelyexamples/: example programsEffcee depends on the RE2 regular expression library.
Effcee tests depend on Googletest and Python.
In the following sections, $SOURCE_DIR is the directory containing the Effcee source code.
git clone https://github.com/google/effcee $SOURCE_DIR cd $SOURCE_DIR/third_party git clone https://github.com/google/googletest.git git clone https://github.com/google/re2.git cd $SOURCE_DIR/
Ensure you have the requisite tools -- see the tools subsection below.
Decide where to place the build output. In the following steps, we'll call it $BUILD_DIR. Any new directory should work. We recommend building outside the source tree, but it is also common to build in a (new) subdirectory of $SOURCE_DIR, such as $SOURCE_DIR/build.
4a) Build and test with Ninja on Linux or Windows:
cd $BUILD_DIR cmake -GNinja -DCMAKE_BUILD_TYPE={Debug|Release|RelWithDebInfo} $SOURCE_DIR ninja ctest
4b) Or build and test with MSVC on Windows:
cd $BUILD_DIR cmake $SOURCE_DIR cmake --build . --config {Release|Debug|MinSizeRel|RelWithDebInfo} ctest -C {Release|Debug|MinSizeRel|RelWithDebInfo}
4c) Or build with MinGW on Linux for Windows: (Skip building threaded unit tests due to Googletest bug 606)
cd $BUILD_DIR cmake -GNinja -DCMAKE_BUILD_TYPE={Debug|Release|RelWithDebInfo} $SOURCE_DIR \ -DCMAKE_TOOLCHAIN_FILE=$SOURCE_DIR/cmake/linux-mingw-toolchain.cmake \ -Dgtest_disable_pthreads=ON ninja
After a successful build, you should have a libeffcee library under the $BUILD_DIR/effcee/ directory.
The default behavior on MSVC is to link with the static CRT. If you would like to change this behavior -DEFFCEE_ENABLE_SHARED_CRT may be passed on the cmake configure line.
Effcee registers two tests with ctest:
effcee-test: All library tests, based on Googletest.effcee-example: Executes the example executable with sample inputs.Running ctest without arguments will run the tests for Effcee as well as for RE2.
The RE2 tests run much longer, so if you're working on Effcee alone, we suggest limiting ctest to tests with prefix effcee:
ctest -R effcee
Alternately, you can turn off RE2 tests entirely by using -DRE2_BUILD_TESTING=OFF at configuration time:
cmake -GNinja -DRE2_BUILD_TESTING=OFF ...
For building, testing, and profiling Effcee, the following tools should be installed regardless of your OS:
On Linux, if cross compiling to Windows:
On Windows, the following tools should be installed and available on your path:
diff.DISABLE_RTTI. Disable runtime type information. Default is enabled.DISABLE_EXCEPTIONS. Disable exceptions. Default is enabled.EFFCEE_ENABLE_SHARED_CRT. See above.RE2_BUILD_TESTING. Should RE2 tests be built? Defaults to ON.We track bugs using GitHub -- click on the “Issues” button on the project's GitHub page.