Right. This should be documented. It's the same issue with
quickbook font styles not being available in the code. In
code sections, quickbook syntax ceases to exist; for a good
reason: to avoid clashing with the syntax of the target
language (C++, Python, etc). I think the best solution, so
far, is to have a target-langauge specifific means to escape
back to quickbook mode:

template <class T>
struct function_traits
{
  static const std::size_t arity = __below;
  typedef __below result_type;
  typedef __below `'''arg<replaceable>N</replaceable>_type'''`;
};

(tick `...` used to escape back to quickbook)

Aside: I think <replaceable>Id</replaceable> is common enough
to have its own quickbook markup. Example:

[replaceable N]

Agreed.

Actually, thinking about it, I'm surprised that I thought it would work. It is important to be able to escape back to quickbook though, if only for linking to other sections from within code.

BTW, I should have said before: I'm really starting to enjoy using quickbook, I wasn't sure to begin with how it would work out, but now I'm certain that it's saved me a whole heap of time.

Finally, a couple more corner cases that don't quite work as expected:

In tables, it's not possible to have an untitled table, I had hoped that if you didn't specify a title then that would "just work", but it grabs the first row of the table and uses that as a title instead.

I notice that the usual markup can't be used inside table titles: so linking doesn't work, nor does macro expansion, it's not a big deal, but should at least be documented.

In any case thanks for an excellent tool!

John.




------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Boost-docs mailing list [email protected] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs

Reply via email to