On 08/14/14 13:50, Dimitry Sibiryakov wrote:
14.08.2014 11:34, Alex Peshkoff wrote:
I do not have access
to that box myself, so I can't report what is actually that format. But
an attempt to access it as we do on windows/linux cause an error.
Do you mean normal access like calling virtual
On 08/14/14 18:24, Tony Whyman wrote:
I was using the Alpha 2 source
may be 16, 15 ...
but definitely not 4
--
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 08/14/14 15:28, Dimitry Sibiryakov wrote:
14.08.2014 11:34, Alex Peshkoff wrote:
HP C/aC++ Version A.06.26
Alpha version?..
don't think so
PS: The problem with FPC which started whole this topic seems to be a
compiler's bug which destroy value returning by external function.
15.08.2014 9:40, Alex Peshkoff wrote:
strange...
I use external functions in the sample of calling c++ from pascal and
returned values are OK
Integers are ok, pointers are ok, interfaces are in trouble.
--
WBR, SD.
On 15/08/14 08:48, Dimitry Sibiryakov wrote:
Integers are ok, pointers are ok, interfaces are in trouble
This should probably be written in stone somewhere.
Even simple external calls such as fb_get_master_interface are difficult
enough. You have carefully define each data type used and ensure
15.08.2014 10:36, Tony Whyman wrote:
You have carefully define each data type used and ensure that
the calling conventions are compatible. Even cdecl starts being a
problem as soon as you get away from simple types - as you have found.
All that I found is:
1) Translating must be done by a
Hello, All.
I've noticed that examples in examples/interfaces has one bug: they don't
check for
interface versions.
Let's see:
st = master-getStatus();
prov = master-getDispatcher();
att = prov-createDatabase(st, fbtests.fdb, dpb - dpbBuf,
On 15/08/2014 13:39, Dimitry Sibiryakov wrote:
Wouldn't be endless checking annoying?..
It looks like in the past days, that's one of the things we were
discussing, no?
Adriano
--
Firebird-Devel mailing list,
15.08.2014 18:43, Adriano dos Santos Fernandes wrote:
It looks like in the past days, that's one of the things we were
discussing, no?
Yes, and you insisted on autoupgrade. That's why the example must be fixed.
--
WBR, SD.
On 15/08/2014 13:45, Dimitry Sibiryakov wrote:
15.08.2014 18:43, Adriano dos Santos Fernandes wrote:
It looks like in the past days, that's one of the things we were
discussing, no?
Yes, and you insisted on autoupgrade. That's why the example must be fixed.
It can be automatically fixed
15.08.2014 18:47, Adriano dos Santos Fernandes wrote:
It can be automatically fixed if/when the new C++ code is placed.
Will you generate call of master-upgradeInterface() in every method that
return an
interface?
--
WBR, SD.
On 15/08/2014 13:49, Dimitry Sibiryakov wrote:
15.08.2014 18:47, Adriano dos Santos Fernandes wrote:
It can be automatically fixed if/when the new C++ code is placed.
Will you generate call of master-upgradeInterface() in every method that
return an
interface?
Only if its version
On 15/08/2014 14:05, Dimitry Sibiryakov wrote:
15.08.2014 18:58, Adriano dos Santos Fernandes wrote:
On 15/08/2014 13:49, Dimitry Sibiryakov wrote:
15.08.2014 18:47, Adriano dos Santos Fernandes wrote:
It can be automatically fixed if/when the new C++ code is placed.
Will you generate
15.08.2014 19:10, Adriano dos Santos Fernandes wrote:
Prepare call will return to its caller a statement where the 13th method
will return a not-implemented error.
How big is overhead?
Will it happen as well with interfaces returned from Y-valve to client
application?
--
WBR, SD.
15.08.2014 20:30, Adriano dos Santos Fernandes wrote:
It's the caller who chooses to upgrade. It may use a no-upgrade police
if he wants.
That's why I think that examples must demonstrate how to do upgrade in
application
right. In case if a programmer choose to play safely.
--
WBR,
Introduce SORTLIST function
---
Key: CORE-4520
URL: http://tracker.firebirdsql.org/browse/CORE-4520
Project: Firebird Core
Issue Type: New Feature
Reporter: Tim Kelly
It would be useful to have a built
16 matches
Mail list logo
