All, We are creating lots of public include files and throwing them in src/include.
I think we should create src/include/firebird directory to put public files. It's how it's going to be placed when installed too, as we can't distribute files named as Interface.h in main /usr/include, for example. So I propose we do it. Files as ibase.h and iberror.h would continue to be in include for backward compatibility. Also, instead of put src/include/firebird in -I in our build, we should include them as firebird/Name.h like public applications will do. Adriano ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
