Re: Spirit X3 employee.cpp compile error
Vincent Virgilio <[email protected]>
| Newsgroups | gmane.comp.parsers.spirit.general |
|---|---|
| Message-ID | <[email protected]> |
On Aug 12, 2016, at 08:27 AM, Larry Evans <[email protected]> wrote: On 08/12/2016 06:40 AM, Larry Evans wrote: [snip] GitHub: [email protected]:boostorg/spirit.git Use the develop branch. --}--cut here-- The 2 template arg rule code is actually in the x3-devel branch instead of the develop branch: https://github.com/boostorg/spirit/blob/x3-devel/include/boost/spirit/home/x3/nonterminal/rule.hpp#L80 [snip] However, if you decide to use x3-devel, then the employee.cpp code referenced in your OP needs to be modified so that the arguments to BOOST_SPIRIT_DEFINE contain assignments instead of just rule names. For example, see: https://github.com/boostorg/spirit/blob/x3-devel/example/x3/calc4.cpp#L218 HTH. -regards, Larry Hi Larry, Thanks for all the help so far. Why is BOOST_SPIRIT_DEFINE required if the rule declarations and definitions are already associated via assignment? In another small project, I was able to parse with an X3 grammar without that macro. In that case, very schematically, I had "auto const rule_name = rule<...>() = rule_def;" I'm limiting myself mostly to the version of X3 included in the latest Boost release (1.61 as of now). I won't be using x3-devel, except for some experiments. Again, thank you. Vince ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohodev2dev _______________________________________________ Spirit-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/spirit-general