Re: How to parse blocks lead by spaces

On 24-03-18 21:32, Dan Bloomquist wrote:

> Scoping is done with leading spaces. I've searched but still at a loss
> as to the right way to do it. My first thought is to read leading
> spaces and create an index. 
That's an option

> The only stuff I want to parse at first is the 'TextStyle' and
> 'Symbol' blocks. So skip 'unknown' blocks for now, add them later as
> needed. 
I'd look at things, but I'm really wanting a specification.

> Is one of the best starting points I've found for the likes of what
> I'm after. And from there, an x3::symbols table?? Reason, I am parsing
> Pins now but with the assumption that the order of the sub objects is
> consistent. That I should parse with any order acceptable as I did in
> 'extra info'. 
In particular, I'm not (yet) seeing how qi::symbols / x3::symbols will
help you grok the whitespace. In fact, I'd think of `qi::locals` there,
which, incidentally, can be hard to get right in x3 land (`x3::with<>`
is not a drop-in replacement behaviourally). So I'm not sure what to advise.

Off-Topic:

> What I'm out to do is parse a decompressed BXL file into my object
It seems a cruel joke that a proprietary firm convinced everyone to use
their "vendor neutral" file format when that format seems not be freely
documented, and people need to use the "Free" reader tools and the
(surprise) paid tooling to create/manipulate these files.

I haven't been able to find a specification, do you have one?


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot