Subject | RE: [Firebird-devel] RE: [Firebird-Architect] Architecture -- Why you should care |
---|---|
Author | Leyne, Sean |
Post date | 2004-04-06T20:35:17Z |
Jim,
the "contract" represented in ibase.h (which has been around for a long
time, back to IB 5.x -- at least) does not reflect the conditions which
you outlined from the ORSI doc.
And, Since ibase.h represents the API reality (like it or not) of the
Firebird/IB world...
The question which needs to be focused on is how can the 32/64 bit
handle issue be best addressed within the limitations of the current
ibase.h definitions?
Sean
> Leyne, Sean wrote:it
>
> >Can you provide a link to this document? (I've already tried to find
> >on the IBP site)(support
> >
> >In all my years of following with Interbase and Firebird lists
> >and Devel), I don't recall this document being mentioned before.(willing
> >
> >So I'm not aware that this document has been publicly available
> >to be shown).has
> >
> >
> It was published by the original Interbase Software Corporation. It
> almost certainly been out of print since the Borland years. We have ahad
> hard copy and are investigating having it scanned. I'm sorry that I
> to reference a generally unavailable document, but I have littlecontrol
> over history. My concern, though, is for the future.While it would be great to see the original document, it would seem that
the "contract" represented in ibase.h (which has been around for a long
time, back to IB 5.x -- at least) does not reflect the conditions which
you outlined from the ORSI doc.
And, Since ibase.h represents the API reality (like it or not) of the
Firebird/IB world...
The question which needs to be focused on is how can the 32/64 bit
handle issue be best addressed within the limitations of the current
ibase.h definitions?
Sean