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
Just looking for some clarification: When writing c and C++ apps, what
is the recommended API?
If the answer is both, are there any trade-offs to be aware of?
Scott
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
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,
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.
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
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
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
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
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 "
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
10 matches
Mail list logo
