module documentation
Get API information encoded in C files.
See find_function for how functions should be formatted, and read_order for how the order of the functions should be specified.
Class |
|
Undocumented |
Class |
|
Undocumented |
Class |
|
Undocumented |
Class |
|
Undocumented |
Class |
|
Undocumented |
Class |
|
Undocumented |
Exception |
|
Undocumented |
Function | check |
Check that an api dict is valid (does not use the same index twice). |
Function | file |
Undocumented |
Function | find |
Scan the file, looking for tagged functions. |
Function | fullapi |
Given a list of api dicts defining the numpy C API, compute a checksum of the list of items in the API (as a string). |
Function | get |
Parse source files to get functions tagged by the given tag. |
Function | get |
Undocumented |
Function | main |
Undocumented |
Function | merge |
Undocumented |
Function | order |
Order dict by its values. |
Function | remove |
Undocumented |
Function | should |
Undocumented |
Function | skip |
Undocumented |
Function | split |
Undocumented |
Function | write |
Write data to filename Only write changed data to avoid updating timestamps unnecessarily |
Constant | API |
Undocumented |
Constant | THIS |
Undocumented |
Constant | VERRE |
Undocumented |
Function | _repl |
Undocumented |
Scan the file, looking for tagged functions.
Assuming tag=='API', a tagged function looks like:
/*API*/ static returntype* function_name(argtype1 arg1, argtype2 arg2) { }
where the return type must be on a separate line, the function name must start the line, and the opening { must start the line.
An optional documentation comment in ReST format may follow the tag, as in:
/*API This function does foo... */
Given a list of api dicts defining the numpy C API, compute a checksum of the list of items in the API (as a string).