Re: Keywords and Namesapces
- Posted by mattlewis (admin) Oct 10, 2011
- 40127 views
Or perhaps you meant to say that having all these functions in a single namespace is the problem, whereas breaking it up as wxWidgets does by class would solve the problem. If this is the case, then I think we have universal agreement that the best thing to do is to break wxEuphoria into namespaces.
Since that's such a big effort, I'm sure the wxEuphoria developers would be happ to accept patches for this.
I've been thinking about this for a while. I think the way to go is probably to rename all of the C++ wrappers. Basically, I'd prefix each one with the name of the file into which they would go. That way, I could continue with my automatic wrapping, as I'd have a way to determine which file should be used.
This doesn't solve the problem of how to deal with functions that are already polymorphic (the polymorphism is handled in the C++ code, either using regular old C++ or the wxWidgets RTTI).
Then comes the issue of porting old code to the new code. At this point, I usually feel compelled to find something else to do...
Matt
