On 23/06/2020 07:46, Dimitry Sibiryakov wrote: > 23.06.2020 12:39, Adriano dos Santos Fernandes wrote: >> That is not good. It makes mandatory that user have the include >> directory where ibase.h is in its include path, which should not be >> necessary. > > firebird is a subdirectory for the one where ibase.h is placed. If a > user writes "#include <firebird/Interface.h>" they already has the > directory in the include path so the problem does not exist. >
No. User is free to copy that directory to its project and put it not in an include path and include the files relative to its source. >> I think we should put ibase.h in firebird directory, maintain the >> include in firebird/Interface.h and add a stub ibase.h that includes >> "firebird/ibase.h" for compatibility. >> >> Opinions? > > Interface.h must not include ibase.h and it was already discussed here. > I talk about what we have (both in v3 and master), not about what we do not have. Even for ibase.h and others legacy headers, the solution to drop various files in a common include directory (like in Linux) should be regarded as compatibility. We should better direct users to include firebird/something.h today, like most libraries and frameworks do. Adriano Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
