Re: [Firebird-devel] ibase.h vs interface.h
On 1/7/21 8:25 PM, Scott Morgan via Firebird-devel wrote: Just looking for some clarification: When writing c and C++ apps, what is the recommended API? For new projects - definitely API in interface.h. Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] ibase.h
23.06.2020 15:26, Adriano dos Santos Fernandes wrote: Users should not change structure of Firebird include files to make them work when they are copied in a project. Why? First of all they must not copy the files into a project. As soon as they do it, the rest is their responsibility, not ours. -- WBR, SD. Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] ibase.h
On 23/06/2020 08:04, Dimitry Sibiryakov wrote: > 23.06.2020 12:58, Adriano dos Santos Fernandes wrote: >> 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. > > In this case they also free to copy ibase.h there. Let's not discuss > clinical idiots that are able to copy only one file. > You simply don't understand! Users should not change structure of Firebird include files to make them work when they are copied in a project. Adriano Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] ibase.h
23.06.2020 12:58, Adriano dos Santos Fernandes wrote: 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. In this case they also free to copy ibase.h there. Let's not discuss clinical idiots that are able to copy only one file. -- WBR, SD. Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] ibase.h
On 23/06/2020 07:50, Alex Peshkoff via Firebird-devel wrote: > On 2020-06-23 13:39, Adriano dos Santos Fernandes wrote: >> Hi! >> >> Here I'm talking mainly on the distribute kits. >> >> Currently we have in firebird/Interface.h a #include "ibase.h". >> >> 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. >> >> 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? > > Do we already have separate parts of ibase.h installed? If yes whole > ibase.h shold better not be included here (it was poor man solution > for 3.0), better include needed parts (like consts_pub) here. > Sure, but never expecting that users changes its include path in the way we want. We should use relative paths. Adriano Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] ibase.h
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 " 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
Re: [Firebird-devel] ibase.h
On 2020-06-23 13:39, Adriano dos Santos Fernandes wrote: Hi! Here I'm talking mainly on the distribute kits. Currently we have in firebird/Interface.h a #include "ibase.h". 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. 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? Do we already have separate parts of ibase.h installed? If yes whole ibase.h shold better not be included here (it was poor man solution for 3.0), better include needed parts (like consts_pub) here. Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] ibase.h
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 " they already has the directory in the include path so the problem does not exist. 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. -- WBR, SD. Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] ibase.h cleanup
On 05/18/11 18:38, marius adrian popa wrote: > I propose that in ibase.h these can be deleted > > #define isc_info_db_impl_isc_aisc_info_db_impl_isc_apl_68K > #define isc_info_db_impl_isc_uisc_info_db_impl_isc_vax_ultr > #define isc_info_db_impl_isc_visc_info_db_impl_isc_vms > #define isc_info_db_impl_isc_sisc_info_db_impl_isc_sun_68k > > Also from the comments area > > /* Disabled, not found anywhere. > BSTREAM* ISC_EXPORT Bopen2(ISC_QUAD*, > > isc_db_handle, > > isc_tr_handle, > const > ISC_SCHAR*, > unsigned > short); > */ Agree with both. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
