On 4/9/15, Roger Binns <rogerb at rogerbinns.com> wrote: > These are the details of what I need: > > For each function, its name, the doc page and fragment, and ideally a > few word description of it (the title on the doc page is fine). > > For each family of constants (eg result codes, extended result codes, > run time limits), the doc page, and a few word description (of the family) > > A JSON or XML file with that would make my life a lot easier.
JSON/XML? Seriously? We eat our own dogfood here, thank you! When you get the data it will be in an SQLite database file! JSON/XML.... Good grief... As it happens, the SQLite documentation build process already parses out most of this and puts it into a database already. If you check-out the documentation sources (https://www.sqlite.org/docsrc/timeline) and successfully build the documentation, it creates a docinfo.db file that contains a lot of what you have requested above. Probably it just needs to be enhanced a little. Most of the relevant information is extracted from sqlite3.h using the https://www.sqlite.org/docsrc/artifact/5c48dd261dbe5804 script. -- D. Richard Hipp drh at sqlite.org
