axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Susantha Kumara" <>
Subject RE: Resolving class name conflicts (for Axis c++ 1.2)
Date Thu, 22 Apr 2004 05:46:09 GMT
+1 for using namespaces.
The Axis C++ API exposed to C services and C clients are a set of static
C style functions. So by adding a prefix (probably a c style prefix) to
all those function names will solve any possible conflict situations.
I suggest the prefixes like Axis_ , AAPI_ or AxisAPI_
-----Original Message-----
From: Samisa Abeysinghe [] 
Sent: Wednesday, April 21, 2004 4:56 PM
To: Apache AXIS C Developers List
Subject: Re: Resolving class name conflicts (for Axis c++ 1.2)
Hi Sanjaya,
    If we use namespaces, would it affect services and clients written
in c?
    If the answer is no then +1 for namespaces.
--- sanjaya singharage <> wrote:
> What would be the best mechanism to resolve class name conflicts in 
> the next Axis c++ release (1.2)?
> Two things are possible
> 1. Use namespaces for Axis c++ classes
> -In this case even if Axis c++ uses some third party libraries that 
> has classes with the same class names as Axis c++, that can be 
> resolved -When a client application uses Axis c++ and some other 
> libraries, class name conflicts between those libraries and axis c++ 
> can be resolved. -This is a feature that was intended to address such 
> conflicts in c++
> 2. Use some prefix for class names and hope that will be unique 
> enough.
> -If by some chance Axis c++ encounters a class with the same class 
> name, with prefix and all, all the class names will need to have their

> prefix changed.
> What are other plus or minus points for these two items? Is there any 
> other approach that we can follow?
> sanjaya.
Do you Yahoo!?
Yahoo! Photos: High-quality 4x6 digital prints for 25ยข

View raw message