| dbo:description
|
- Software (de)
- perangkat lunak (in)
- програмне забезпечення (uk)
- Software (de)
- perangkat lunak (in)
- програмне забезпечення (uk)
|
| dbo:license
| |
| dbo:programmingLanguage
| |
| dbo:wikiPageWikiLink
| |
| dbp:author
| |
| dbp:license
| |
| dbp:name
| |
| dbp:programmingLanguage
| |
| dbp:text
|
- For PyQt v4 I use an internal tool called . This is sort of an IDE for SIP. It uses GCC-XML to parse the latest header files and saves the relevant data, as XML, in a project. then does the equivalent of a diff against the previous version of the API and flags up any changes that need to be looked at. Those changes are then made through the GUI and ticked off the TODO list. Generating the files is just a button click. In my subversion repository, PyQt v4 is basically just a 20M XML file. Updating PyQt v4 for a minor release of Qt v4 is about half an hours work.
In terms of how the generated code works then I don't think it's very different from how any other bindings generator works. Python has a very good C API for writing extension modules - it's one of the reasons why so many 3rd party tools have Python bindings. For every C++ class, the SIP generated code creates a corresponding Python class implemented in C. (en)
|
| dbp:title
|
- developer and maintainer (en)
|
| dbp:wikiPageUsesTemplate
| |
| dct:subject
| |
| gold:hypernym
| |
| rdf:type
| |
| rdfs:label
| |
| owl:sameAs
| |
| prov:wasDerivedFrom
| |
| foaf:isPrimaryTopicOf
| |
| foaf:name
| |
| is dbo:programmingLanguage
of | |
| is dbo:wikiPageDisambiguates
of | |
| is dbo:wikiPageWikiLink
of | |
| is foaf:primaryTopic
of | |
