axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Samisa Abeysinghe <samisa_abeysin...@yahoo.com>
Subject RE: Resolving class name conflicts (for Axis c++ 1.2)
Date Thu, 22 Apr 2004 07:23:09 GMT
Hi Susantha,
   Yes C++ projects use folders. But Axis C++ is not pure C++.
   There is a C interface as well.
   Why not use a file name prefix as in apache web server?
   Why do we have to use folders? Are there any specific advantages of using folders?
Thanks,
Samisa...

--- Susantha Kumara <susantha@opensource.lk> wrote:
> Hi Samisa,
> 
> Its true that having Call.h will restrict you to place another Call.h
> from another library or so. Usually this is problem is solved by having
> #includes with the folder name in front. Ex:
> 
> Use #include <axis/Call.h> instead of #include <Call.h> . Xerces C++
> uses this convention. And most of the C++ projects too.
> 
> ---
> Susantha
> 
> -----Original Message-----
> From: Samisa Abeysinghe [mailto:samisa_abeysinghe@yahoo.com] 
> Sent: Thursday, April 22, 2004 12:36 PM
> To: Apache AXIS C Developers List
> Subject: RE: Resolving class name conflicts (for Axis c++ 1.2)
> 
> Hi Susantha,
> 
> > Header file names wont conflict (no compilation issues). But are you
> > suggesting that we have a prefix for file names so that Axis C++ API
> > header files look unique ?.
> 
> Have a look at perious message thread by Jean-Yves
> (http://marc.theaimsgroup.com/?l=axis-c-dev&m=108260093514665&w=2)
> I feel his argument is valid and there would be Header file name
> conflicts.
> 
> Thanks,
> Samisa...
> 
> 
> 	
> 		
> __________________________________
> Do you Yahoo!?
> Yahoo! Photos: High-quality 4x6 digital prints for 25
> http://photos.yahoo.com/ph/print_splash
> 
> 
> 



	
		
__________________________________
Do you Yahoo!?
Yahoo! Photos: High-quality 4x6 digital prints for 25
http://photos.yahoo.com/ph/print_splash

Mime
View raw message