Hi Christian,
Now I’m still on it, I’ve another thought; c.q. request.
With closures as datastructures we’re half way an OOP’ish-implementation.
The other half concerns class-methods.
Modules work pretty good here, ( now it comes) however it would be nice if some sort of inheritance could be implemented.
For example: I store my map:update-function ( see my previous mail) with some other map-sugar functions in “XQR.map”-module, which is just an extension in the BaseX map-module.
If I don’t want to be put up with both modules in my program, which for obvious reasons is a good attitude, I have to redirect all standard map-function calls in my self defined XQR.map-module to Basex’s map-module.
But now I find myself programming these redirections, which, for the same obvious reasons, is not an optimal situation.
I was wondering if there is or maybe can be created, an easy way to redirect unresolved function calls within a module to a specified module. With or without entering W3C-territory.
What’s your opinion on this?
Rob Stapper
![]() |
Dit e-mailbericht is gecontroleerd op virussen met Avast antivirussoftware.
|