Are you happy with your logging solution? Would you help us out by taking a 30-second survey? Click here


C++ Frequently Questioned Answers (FQA)

Subscribe to updates I use cpp-fqa

Statistics on cpp-fqa

Number of watchers on Github 197
Number of open issues 1
Main language Python
Average time to merge a PR about 23 hours
Open pull requests 0+
Closed pull requests 0+
Last commit over 2 years ago
Repo Created almost 4 years ago
Repo Last Updated over 1 year ago
Size 359 KB
Organization / Authoryosefk
Page Updated
Do you use cpp-fqa? Leave a review!
View cpp-fqa activity
View on github
Fresh, new opensource launches 🚀🚀🚀
Trendy new open source projects in your inbox! View examples

Subscribe to our mailing list

Evaluating cpp-fqa for your project? Score Explanation
Commits Score (?)
Issues & PR Score (?)

This is the source code for the C++ FQA published at

You're very welcome to edit the FQA; in particular, it's not up to date with C++11/14/etc., nor with the new FAQ structure (I mean the new, erm, they call it Super-FAQ at

software: - *.fqa -> *.html. master script doing it all. - converts .fqa files to .html files. does most of the work, but not all. - module generating TOC from

headings and a <!-- h2toc --> comment. modifies files inplace. follows fqa2html - makes the html w3c-compliant, and runs tidy to make sure it really is. - uploads all *.html files generated from *.fqa files to slow, but automatic. - manual. generates html code for link faces (for linking.html).


*.fqa - FQA sources. *.html - final generated FQA web pages. images are stored at the server.

syntax of *.fqa pages:

A paragraph is text between two blank lines:

This is a paragraph.

This is another paragraph.

Currently for say 2 blank lines the program barfs, sigh.

A FAQ entry looks like this:

Question-paragraph (single line)

FAQ: rest of paragraph

maybe more paragraphs

FQA: rest of paragraph

maybe more paragraphs


The program creates a link to the C++ FAQ question at FAQ:. In the original C++ FAQ, questions are linked to by number. In the FAQ, questions have named links so if we switch to linking to we'd need to handle that difference.

Special syntax inside paragraph text:

/whatever/ becomes whatever (italics) \/ becomes /, escaping the syntax above |whatever| becomes whatever (teletype font - used for code) [18.2 whatever] becomes a hyperlink to FQA answer 18.2. /[corr.3 (correction)]/ becomes a hyperlink to correction 3, in italics, with (correction) as the link text. [ whatever] becomes a hyperlink to whatever becomes whatever, unescaped - for instance < becomes <, unlike < which becomes <. this is used for

  • , and

    . @ paragraph @ ...becomes
    . /whatever/ inside @...@ still becomes whatever so \/ must be used to spell /.

    Now to the general page structure: there are two kinds of pages, FAQ-section-mirroring pages and general pages. A FAQ-section-mirroring page has as its first paragraph something like this:

    Title sentence {'section': 40, 'faq-page': 'whatever.html'} Description sentences

    The dictionary is used for question numbering and hyperlink generation.

    A general page looks like this:

    Title sentence {} Description sentences

    Possibly more paragraphs

    `<!-- h2toc -->



    <h2>another heading</h2>

    More paragraphs


    Here the table of contents - links at the top of the page - is generated from hand-coded

    headings (unlike FAQ-section-mirroring pages where it's generated from question titles.)

cpp-fqa open issues Ask a question     (View All Issues)
  • over 3 years C++ FAQ Lite is now C++ FAQ
cpp-fqa list of languages used
More projects by yosefk View all
Other projects in Python