Hi Pritpal, It's highly unlikely that function names or namespaces are copyrighted.
This is rather a design and package management issue. If you use original Xbase++ names, you create a potential name collision with another tool trying to implement the same thing. In practice this could be a problem if two overlapping subsets of these functions are implemented by two competing libs. Users won't be able to use both at the same time. A likely scenario for this is when user has some local partial implementations of some XPP classes, and will now experience collisions. In the case of GTWVG this doesn't seem very likely. I'd personally do the renaming after GTWVG is proven to be working properly, now it seem a bit early yet. Much more important would be to resolve the violation of WVT* and WIN*() namespaces in GTWVG, and last but not least the build-breaker MSVC GPF, and the meaningful warnings. [ posted on the list a while ago. ] Brgds, Viktor On Tue, Feb 10, 2009 at 3:37 AM, Pritpal Bedi <[email protected]>wrote: > > Hi Everybody > > I need some clarification on the issue > related with function names used from one > compiler in another. > > I am implementing Xbase++ parts in GTWVG and > all classes have a prefix of WVG*(). In Xbase++ naming > of classes is prefixed with Xbp*(). This necessiates > an a .ch #xtranslating WVG* => XBP* to compile > an Xbase++ prg in Harbour. > > What if I change WVG* to XBP* and Xbase++ .ch > files constants. > > Regards > Pritpal Bedi > -- > View this message in context: > http://www.nabble.com/Copyright-Information-about-Function-Names-tp21926594p21926594.html > Sent from the Harbour - Dev mailing list archive at Nabble.com. > > _______________________________________________ > Harbour mailing list > [email protected] > http://lists.harbour-project.org/mailman/listinfo/harbour >
_______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
