Re: Some reflections on using quickbook

Reece Dunn wrote:
> Joel de Guzman wrote:
> > Reece Dunn wrote:

> > > 4.  Code - adjacent code fragments aren't concatenated:
> > >
> > > [For example:
> > >   ``int foo()``
> > >   ``{``
> > >   ``}``
> > > ]
> >
> >
> > Shouldn't that be:
> ....
>
> >   ``
> >   int foo()
> >   {
> >   }
> >   ``
>
> ....
>
> > ??
>
>
> But if there is whitespace before the code text (as indicated by the 
> .... I added for illustrative purposes) then the whitespace is retained 
> and if this is indented to contain a large number of spaces, the code 
> doesn't look good. Also, doesn't your example add newlines above and 
> below? What if I wanted to avoid that?

None :(

> > > 5.  Code fragments spanning multiple lines retain all whitespace, 
> > > thus the code fragment:
> > >
> > > [For example:
> > >   ``int foo()
> > >     {
> > >        std::cout << "bar" << std::endl;
> > >     }``
> > > ]
> > >
> > > gets incorrectly formatted w.r.t. spacing.
> >
> >
> > What were you expecting?
>
>
>  From the way it currently works, something like
>
> int foo()
>      {
>         ...
>      }
>
> Ideally, I'd like it to see the opening `` and note the number of 
> whitespace before it (adding two for the `` marker) then removing that 
> much whitespace from each subequent line, giving:
>
> int foo()
> {
>    ...
> }
>
> It's ok if this is not implemented as there are ways around it.

Yeah. Acknowledged. I'll see if there's a nice way
around this. I think this should be fixed in preparation
to the planned Lit programming support with code stacks
and all.

> I've also noticed that:
>
> [table
> [[...] [...] [...]]
> [[Minimize CRT Use in ATL] [Foo] [
> ATL is not natively supported in BBv2, so this is the default.
> ``feature atl-minimum-crt : no yes : propagated composite ;
> feature.compose <atl-minumum-crt>yes : <define>_ATL_MIN_CRT ;``
> ]]
>
> [[Minimize CRT Use in ATL] [Bar] [
> ATL is not natively supported in BBv2, so this is the default.
>
> ``feature atl-minimum-crt : no yes : propagated composite ;
> feature.compose <atl-minumum-crt>yes : <define>_ATL_MIN_CRT ;``
> ]]
> ]
>
> The table row containing "Foo" will compile cleanly, but "Bar" will 
> generate syntax errors (note the additional line spacing).

Yep. Phrases, in general, cannot have double newlines,
except if they are in a pre markup. It might be possible
to allow double newlines in block_markup(s) because the
closing bracket terminates it anyway. I'll see if that can
be done.

Cheers,
--
Joel de Guzman
http://www.boost-consulting.com
http://spirit.sf.net



-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Boost-docs mailing list
Boost-docs@xxxxxxxxxxxxxxxxxxxxx
Unsubscribe and other administrative requests: 
https://lists.sourceforge.net/lists/listinfo/boost-docs