boost-spirit-x3

As my parser grows I separated some rules into different translation units (TU) and the linker problem rises. After weeks of several try&errors without success I reduced my ~50 rules to the (hopefully) minimal example presented here. I've read the related linking errors while separate parser using boost spirit x3 and checked, that I use at the context typedef iso8859_1::space_type and that I invoke iso8859_1::space later on. Also I don't let the compiler deduce the iterator_type. The linker error I made more fancy by replacing some things: In function `bool x3::rule<parser::string_literal

Trying to generate an AST like the employee example that has more than just the employee. In my current mindset, the RExpressions example isn't helping me. The example I have doesn't compile, but I went as far as I understood in adding teams, departments, and corporations to the employee example. My problem is in understanding how to add the different structs into a variant and add the variant to phrase_parse, if that's the idea. In this example, there can be several of the same lines following each other. So wondering if that's what requires making an AST recursive. #include <boost/config

(1) Say we want to parse a simple recursive block surrounded by {} . { Some text. { { Some more text. } Some Text again. {} } } This recursive parser is quite simple. x3::rule<struct idBlock1> const ruleBlock1{"Block1"}; auto const ruleBlock1_def = x3::lit('{') >> *( ruleBlock1 | (x3::char_ - x3::lit('}')) ) >> x3::lit('}'); BOOST_SPIRIT_DEFINE(ruleBlock1) (2) Then the block becomes more complex. It could also be surrounded by [] . { Some text. [ { Some more text. } Some Text again. [] ] } We need somewhere to store what kind of opening bracket that we have. Since x3 does not have locals, we

This is a follow-up on this Q&A . I now have several data structures in a namespace ast , subdivided over two sub-namespaces ( algebraic and numeric ) that correspond to the two different formats that the grammar recognizes. namespace ast { namespace algebraic { struct occupance { char pc; char col; int row; }; using pieces = std::vector<occupance>; struct placement { char c; boost::optional<pieces> p; }; } namespace numeric { struct occupance { char pc; int sq; }; struct range { occupance oc; int sq; }; using pieces = std::vector<boost::variant<range, occupance>>; struct placement { char c;

Change my codes from QI to X3, and get some compile error with BOOST_FUSION_ADAPT_ADT . I tried boost 1.64 and 1.67, neither of them work. I modified the spirit X3 example rexpr_min , adding getter and setter to struct rexpr , changing the BOOST_FUSION_ADAPT_STRUCT to BOOST_FUSION_ADAPT_ADT , and compile it fail, too. Enviroment: ubuntu 16.04 G++ 5.4, with -std=c++17 flag boost 1.67 Error message: boost/spirit/home/x3/core/detail/parse_into_container.hpp:142:35: error: invalid initialization of non-const reference of type ‘boost::fusion::extension::adt_attribute_proxy<client::ast::rexpr, 0,

I am trying to use Boost Spirit X3 with semantic actions while parsing the structure to an AST. If I use a rule without separate definition and instantiation it works just fine, for example: #include <vector> #include <string> #include <iostream> #include <boost/fusion/include/adapt_struct.hpp> #include <boost/spirit/home/x3.hpp> namespace ast { struct ast_struct { int number; std::vector<int> numbers; }; } BOOST_FUSION_ADAPT_STRUCT( ast::ast_struct, (int, number) (std::vector<int>, numbers) ) namespace x3 = boost::spirit::x3; using namespace std; void parse( const std::string &data ) { string