axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjiva Weerawarana" <sanj...@opensource.lk>
Subject Re: Flat header structure
Date Tue, 06 Jul 2004 17:07:06 GMT
+1 for retaining at least <axis/Call.h> model .. that allows a
chance to disambiguate at least visually.

Sanjiva.

----- Original Message ----- 
From: "Kenneth Chiu" <chiuk@cs.indiana.edu>
To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Sent: Tuesday, July 06, 2004 4:33 PM
Subject: Re: Flat header structure


> On Mon, 5 Jul 2004, Samisa Abeysinghe wrote:
> > I understand that there is some file location restructuring is going on.
> >
> > I would like to propose a flat header structure for the header files.
> > e.g.
> > instead of having
> > #include <axis/client/Call.h>
> > to have
> > #include <Call.h>
> >
> > At the moment there are client and server sub folders in include/axis.
> > Some of the generic ones used both by client and server are in server
sub folder.
> > There are only 2 files in client sub folder.
> > Hence it would be quite simple to have all the files in one place and
have a simple include
> > structure.
> >
> > As the API ducumentation could do the categorization and also give ample
details to the users, I
> > think it is a good idea to drop the nested structure in the include
statement.
> > In case there are going to be any concerns related to name conflicts,
namespaces and or prifixes
> > culd be used.
>
> It's a good idea to have at least one level in your
> directory structure to avoid file name conflicts.  For
> example, a user might be trying to include some other file
> named Call.h.
>
> >
> > Thanks,
> > Samisa...
> >
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > New and Improved Yahoo! Mail - Send 10MB messages!
> > http://promotions.yahoo.com/new_mail
> >
>


Mime
View raw message