Draft for 1.0 release
This is a draft for the upcoming 1.0 version, which plans to outdate the
current test release 0.x.
Calls to DOM functions
The upcoming 1.0 release is more DOM2 compliant. The concept of unit will be removed,
since we can refer to every object in the dom tree, included the DomDocument itself,
with the numeric ID returned by an opportune createDocFromURI, in resemble to gdome2
style. Moreover, every object managed by f77xml will have a numerical ID, even
For the calling convention, I choose a more useful approach. For example,
suppose we have the function gdome_el_firstChild. The prototype for this function is
GdomeNode* gdome_el_firstChild (GdomeElement *self, GdomeException *exc);
Our objective for the 1.0 release is to create subroutines for f90 that can be
rewritten as f77 calls from the preprocessor. For this reason, the hypothetical
f90 subroutine is in the form:
Thus, for example, the gdome_el_firstChild is mapped as
since nodeCode is an integer, we could rely on functions, instead of
subroutines. This is a debatable argument.
The mapping to f77 will:
- parse the f77xml_el_firstChild(nodeCode,elemCode,err)
- extract the el_firstChild
- extract the first argument (nodeCode) which is the return value
- extract the remaining arguments (elemCode,err)
- lookup the el_firstChild in the signature database. This returns p3t1
- create the code as
Please note that the 1.0 are different from the 0.x signatures.
Also please note that all
function names for multiplexing) are
identified by codes.
This means that you need to write, for example
integer doc ! the domDocument object
Although all these changes seems to destroy what i stated in the first draft,
this new approach carry a lot of improvements:
- there's a clean correspondence between the gdome2 functions and the f77xml ones
- the namespace pollution is even more reduced, since c|se type functions now are c|ce.
Please note that i divide the return value from the parameters using a pipe |
- Managing string is no more an issue. The returned object can be queried
for length, or for substring, for example. A set of subroutines is implemented to support