Re: [Spirit Qi %] (x%y) not semantically equivalent to (x >> *(y >> x))

On 29/05/2016 11:28 PM, Lee Clagett wrote:
> If the list parser does not meet your expectations or needs, then it is
> an inconvenience to you but not necessarily a "bug that became a
> feature". Joel has not said anything specifically about this topic, but
> I am fairly certain the intent of the list parser was to omit the
> separator from the exposed attribute. In the majority of cases
> the separator value is irrelevant. For cases where this is not true,
> the more verbose way of producing the identical parser is still
> available.

It is the intent, yes. Indeed, in the majority of cases the separator
value is irrelevant. That has been the case with Qi and now with X3.
As always, the goal is to make it easy for the majority of cases, and
if possible, provide other means for other cases. I think that is what
we have here.

If this is unclear, then it is a documentation matter and thus I
will welcome any contributions to explain the issue better.

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