Re: Possible regression in boost 1.61
Joel de Guzman <[email protected]>
| Newsgroups | gmane.comp.parsers.spirit.general |
|---|---|
| Message-ID | <[email protected]> |
On 26/05/2016 9:33 PM, Peter Gerell wrote: >> Oh, right, my bad. What we really need to know is the definition of start_rule. It should be something like the linker error you are having. > > I think I have nailed it. > I had to change from > using start_type = x3::rule<start_class, ast::Start>; > to > using start_type = x3::rule<start_class, ast::Count>; > as the start rule contains a single count rule after the result of the preceeding character parser is omitted. > The attribute type of the count rule seems to propagate to the start rule. > > I have not yet tried to fix my original problem. > > It seems this is not a regression, but a breaking change. > I have no problem requiring boost 1.61+ for the project to build. Hmmm, not sure I understand. Can you please elaborate? Why is it a breaking change? Regards, -- Joel de Guzman http://www.ciere.com http://boost-spirit.com http://www.cycfi.com/ ------------------------------------------------------------------------------ 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. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e