Home | Libraries | People | FAQ | More |
“Examples of designs that meet most of the criteria for "goodness" (easy to understand, flexible, efficient) are a recursive-descent parser, which is traditional procedural code. Another example is the STL, which is a generic library of containers and algorithms depending crucially on both traditional procedural code and on parametric polymorphism.” --Bjarne Stroustrup
This document is roughly divided into 3 parts:
Some icons are used to mark certain topics indicative of their relevance. These icons precede some text to indicate:
Table 1. Icons
Icon |
Name |
Meaning |
---|---|---|
|
Note |
Generally useful information (an aside that doesn't fit in the flow of the text) |
|
Tip |
Suggestion on how to do something (especially something that is not obvious) |
|
Important |
Important note on something to take particular notice of |
|
Caution |
Take special care with this - it may not be what you expect and may cause bad results |
|
Danger |
This is likely to cause serious trouble if ignored |
This documentation is automatically generated by Boost QuickBook documentation tool. QuickBook can be found in the Boost Tools.
Please direct all questions to Spirit's mailing list. You can subscribe to the Spirit Mailing List. The mailing list has a searchable archive. A search link to this archive is provided in Spirit's home page. You may also read and post messages to the mailing list through Spirit General NNTP news portal (thanks to Gmane). The news group mirrors the mailing list. Here is a link to the archives: http://news.gmane.org/gmane.comp.parsers.spirit.general.