aboutsummaryrefslogtreecommitdiffstats
path: root/src/mesa/glapi/glX_doc.py
Commit message (Collapse)AuthorAgeFilesLines
* Mammoth update to the Python code generator scripts that live inIan Romanick2005-06-211-48/+63
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | src/mesa/glapi. Basically, the scripts that did simple things (like gl_offsets.py) were simple, and the scripts that did more complicated things (like glX_proto_send.py) were getting progressively more and more out of control. So, I re-write the foundation classes on which everything is based. One problem with the existing code is that the division between the GL API database representation and the way the output code is generated was either blury or nonexistant. The new code somewhat follows the Model-View-Controller pattern, minus the Controller. There is a distinct set of classes that model the API data, and there is a distinct set of classes that generate code from that data. One big change is in the class that represents GL functions (was glFunction, is now gl_function). There used to be an instance of this calls for each function and for each alias to that function. For example, there was an instance for PointParameterivSGIS, PointParameterivEXT, PointParameterivARB, and PointParameteriv. In the new code, there is one instance. Each instance has a list of entrypoint names for the function. In the next revision, this will allow a couple useful things. The script will be able to verify that the parameters, return type, and GLX protocol for a function and all it's aliases match. It will also allow aliases to be represented in the XML more compactly. Instead of repeating all the information, an alias can be listed as: <function name="PointParameterivARB" alias="PointParameterivEXT"/> Because the data representation was changed, the order that the alias functions are processed by the scripts also changed. This accounts for at least 2,700 of the ~3,600 lines of diffs in the generated code. Most of the remaining ~900 lines of diffs are the result of bugs *fixed* by the new scripts. The old scripts also generated code with some bugs in it. These bugs were discovered while the new code was being written. These changes were discussed on the mesa3d-dev mailing list back at the end of May: http://marc.theaimsgroup.com/?t=111714569000004&r=1&w=2 Xorg bug: 3197, 3208
* Refactor a bunch of common code from the "leaf" scripts to a new functions,Ian Romanick2005-04-181-14/+1
| | | | parse_GL_API, in gl_XML.py.
* Convert all Python scripts to use XML namespaces.Ian Romanick2005-04-181-1/+1
|
* Small refactor. Add glXFunctionIterator, which derrives fromIan Romanick2005-02-021-4/+4
| | | | | | | | | | | | | glFunctionIterator and is used by GlxProto. The difference between the two iterator classes is that glXFunctionIterator skips functions that the GLX protocol code does not care about. Replace all the remaining occurances of glParameter::p_count_parameters and glFunction::count_parameters with the count_parameter_list. Add GlxProto::size_call to generate the C code to calculate 'compsize'. These trivially modify the generated code.
* Slightly modify the meaning of the 'handcode' attribute in a 'glx' element.Ian Romanick2005-01-281-1/+1
| | | | | | | | | | | The attribute can now take one of 4 states. "false" (the default value) means that no handcoding is required for the function. "client" means that the function must be handcoded on the client-side only. "server" means that the function must be handcoded on the server-side only. "true" menas that the function must be handcoded on both the client-side and the server-side. Version 1.14 of glX_proto_send.py accidentally contained a line of this change.
* Script to generate rough GLX protocol documentation (as might be seen inIan Romanick2005-01-071-0/+278
an extension spec). It's not perfect, and it doesn't support certain functions that other scripts here can (e.g., pixel functions). However, it is a good start and has already proven useful to me.