Joel de Guzman wrote:
John Maddock wrote:
2) I notice that [endsect] only works if there is a proceeding *blank
line*, otherwise a literal "[endsect]" gets put in the last paragraph
in the xml output. I'm not sure that this is a new issue, but if it's
part of the grammar then it really should be documented. It's also
asymmetrical, since [section] tags don't need a newline following
them, is there any reason why [endsect] shouldn't always be special,
and implicitly end a paragraph?
I'll check this out.
Okidoki... It's not really the [endsect] in question here. It is
the paragraph; and it's documented. Paragraphs start left-flushed
and are terminated by two or more newlines. So, if an [endsect]
ends a paragraph as in (indented for clarity):
blah blah blah
[endsect]
The literal [endsect] becomes part of the paragraph.
The grammar for paragraph goes somewhat like this:
paragraph = +line >> +eol;
where each line is ended by a single eol, hence the paragraph
ends with 2 or more eols. It was my thinking that, in the
absence of explicit markup, this is a reasonable behavior.
For example (indented for clarity):
this is a paragraph X
this is part of the same paragraph X
this is a different paragraph Y
If this behavior is not intuitive, let me know and I might find
a reasonable workaround (allowing simple block-ends like
[endsect] to terminate a paragraph).
Regards,
--
Joel de Guzman
http://www.boost-consulting.com
http://spirit.sf.net
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Boost-docs mailing list
[email protected]
Unsubscribe and other administrative requests:
https://lists.sourceforge.net/lists/listinfo/boost-docs
