Joel de Guzman <joel <at> boost-consulting.com> writes:

> 
> James Fowler wrote:
> > I've put a snapshot of my latest twisted up version of QuickBook at 
> > http://www.openseaconsulting.com/boost/qb20050306.zip.  

James, I'll take a look at this soon. In the meanwhile...

[snip]

> Don't you think we ought to just standardize on a quickbook
> inline syntax for this?

Agreed. I'll have a think.

> >                 + anything else is considered source code, so [include
> >                   ../example/simple_example.cpp] does the "right thing"
>  >                 + common source code extensions [py/h/hpp/c/cpp/...]
>  >                   will automatically pre-select the right source mode
>  >                   for highlighting
> 
> I think we ought to have the extensions in the syntax definition.
> For example:
> 
>      "cpp" { extensions = "cpp"|"hpp"|.... }

Good idea. I would suggest we simply extend the highlighting scheme semantics:

"c++|cxx|C++|cpp|cc" 
{
    "preprocessor" = "^\s*#\s*[[:alpha:]|_]\w*" ;

...
}

This will already get parsed correctly. I just need to do some work under the
bonnet.





-------------------------------------------------------
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