Mail Archives: djgpp/1999/12/04/13:38:17
Thanks to both yourself and Damian for the advice. I probably should have
explained that DataEase is a DOS-based database package. CDF's are a way of
achieving things which it's built-in language, DQL, can't do, by using a
'proper' programming language. Based on your advice and other information I
have come to the decision that my problem lies with the fact that DataEase
is a 16-bit application and so it probably expects things like CDF's to be
compiled using a 16-bit compiler. So I'll probably try Borland Turbo C 2
(circa 1989), which I can get for free from Borland's website :-). Hopefully
that should solve the immediate problem at least.
Thanks again for the advice,
Matt
Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote in message
news:Pine DOT SUN DOT 3 DOT 91 DOT 991130090355 DOT 24907B-100000 AT is...
>
> On Sun, 28 Nov 1999, Matt Pemberton wrote:
>
> > I am trying to create a Custom Defined Function for DataEase
(Version 5,
> > 16M edition).
>
> What is DataEase? Does it come as an object file library? If so,
> your problem is much more serious than what you seem to think: linking
> DJGPP with object files produced by other compilers usually doesn't
> work. See section 17.5 of the DJGPP FAQ for more details.
>
> > The DataEase manual tells me I can do this 'in any language
> > which supports the use of far pointers and the pascal calling
convention'.
>
> To get functions that use Pascal calling convention, use the `stdcall'
> attribute, it's described in the GCC docs. As for `far', simply
> define it away; section 17.7 of the FAQ shows how.
>
> But the fact that DataEase wants `far' probably means that it uses
> either real-mode code or 16-bit protected-mode code. Both are
> incompatible with DJGPP.
- Raw text -