Re: Possible regression in boost 1.61
Peter Gerell <[email protected]>
| Newsgroups | gmane.comp.parsers.spirit.general |
|---|---|
| Message-ID | <[email protected]> |
> If this "new" behavior is according to the documentation, then it is a bug > fix alright. Yes, I recall (myself or someone else) working on this fix, > among others. I could get my parser to build by changing attribute type for my start rule. Unfortunately this doesn't work semantically as it is no longer possible to distinguish between different rules when writing my overloads for operator() in the visitor for my variant for the rule that uses these rules. Strangely I get a different behavior if I recreate the parser in a single translation unit. I have published an example that works with both boost 1.60 and 1.61. Here the start rule get the attribute type I expected. What could be the difference when the parser is split into several translation units? http://coliru.stacked-crooked.com/a/090d820540d20fec Regards, Peter ------------------------------------------------------------------------------ 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