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.
Constant | API_FILES |
Undocumented |
Constant | THIS_DIR |
Undocumented |
Constant | VERRE |
Undocumented |
Class | BoolValuesApi |
Undocumented |
Class | Function |
Undocumented |
Class | FunctionApi |
Undocumented |
Class | GlobalVarApi |
Undocumented |
Class | NonNull |
Undocumented |
Class | ParseError |
Undocumented |
Class | StealRef |
Undocumented |
Class | TypeApi |
Undocumented |
Function | _repl |
Undocumented |
Function | check_api_dict |
Check that an api dict is valid (does not use the same index twice). |
Function | file_in_this_dir |
Undocumented |
Function | find_functions |
Scan the file, looking for tagged functions. |
Function | fullapi_hash |
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_api_functions |
Parse source files to get functions tagged by the given tag. |
Function | get_versions_hash |
Undocumented |
Function | main |
Undocumented |
Function | merge_api_dicts |
Undocumented |
Function | order_dict |
Order dict by its values. |
Function | remove_whitespace |
Undocumented |
Function | should_rebuild |
Undocumented |
Function | skip_brackets |
Undocumented |
Function | split_arguments |
Undocumented |
Function | write_file |
Write data to filename Only write changed data to avoid updating timestamps unnecessarily |
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... */