Julio M. Merino Vidal wrote:
But my point was about the following. At the moment, include syntax is one of:
[include file.qbk] [include:some-id file.qbk]
If the command is changed to be general such as:
[include<:id> <file> <format> <section>]
The new syntax could allow the following incorrect constructions:
[include file.xml xml some-section]
As XML files are included with a specific tag, the parser cannot do anything about the section. So the user could get unexpected results if he gave a section name.
[include:some-id file.cpp]
The some-id has a meaning when including Quickbook documents, but not source code.
Anyway, this is not such a big problem. Quickbook could detect such incorrect cases and raise an error so that the user could correct his code.
Yes. That's an issue of syntax vs. semantics. The incorrect usage you noted clearly fall under semantics, hence, is not a concern of the parser proper. Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net