I vote for=20

Having namespaces for = C++ and=20 having prefixes for C API functions=20
Keeping the existing = folder=20 structures as is=20
Resolving nested = #includes and=20 moving non-API header files from /include/ folder to /src folder

---

Susantha

---

Spend 5 minutes a day to see the beauty of a=20 tree

---

-----Original=20 Message-----
From: = Samisa=20 Abeysinghe [mailto:samisa_abeysinghe@yahoo.com]
Sent: Friday, April 23, 2004 = 10:13=20 AM
To: Apache AXIS C = Developers=20 List
Subject: RE: = Resolving=20 class name conflicts (for Axis c++ 1.2)

Hi = All,

Can = we come to a=20 conclusion on this?

We = got to decide=20 on C++ classes (namespaces or prifixes) c = functions(prefix) and=20 API header file include folder structure and header file=20 names.

There are = two concerns=20 here,

1. = nested #include=20 stucture (flat or not)

2. = Name conflicts=20 (namespaces or prifixes)

(may be we can=20 vote)

Thnaks,

Samisa...

susantha@opensource.lk=20 wrote:

Hi Samisa,

I think = there is no=20 need to follow C styles everywhere because at the
moment there is = no=20 intention to gradually make Axis C++ Axis C. But in
order to = achieve=20 performance and stability we are planning get rid of STL.

> = Hi=20 Susantha,
> Yes C++ projects use folders. But Axis C++ is not = pure=20 C++.
> There is a C interface as well.
> Why not use a = file name=20 prefix as in apache web server?

Of course We can use file name = prefixes=20 instead of namespaces. But that is
a lot of work. For an example = Call class=20 will be Axis_Call

> Why do we have to use folders? Are = there any=20 specific advantages of
> using folders?

I think you are = here=20 talking about having folders to categorize include
files. We do = this=20 because we need to categorize them so that the client
developers = will need=20 only the set of include files in
/include/axis/client/ and server = developer=20 will need only
/include/axis/server/

If we are going to get = rid of=20 folders
1. Call class will be Axis_Client_Call because we also = need to make=20 the
file name same as class name
2. In order to have a = consistency we=20 may need to get rid of folder
structure of /src/ too. This is then = going to=20 be a re-structure of whole
codebase.

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

Do you Yahoo!?
Yahoo! = Photos: High-quality=20 4x6 digital prints for = 25=A2