Stephen Quinn wrote:
> [..]
>> (Clipper 5.2b, Class(y) 2.4b, Clip-4-Win 2, Funcky, Novlib, SixNSX 3,
> If your still using 5.2b then I suggest the first thing to do is upgrade
to 5.2e
Oops, sorry, that was a typo; we use Clipper 5.2e of course.. :)
> [..]
> I'd also suggest you use Blinker or Causeway (freely available now) to
re-link your app in extended mode & dump RUN for
> Blinkers SwpRunCmd() (if you have Blinker that is<g>).
Yes, we already use Blinker 7, as we have been experiencing the 667 Eval
stack error for a couple of years now, and hoped to resolve this issue
Blinker, as it optimizes DGROUP memory. However, as our app keeps
growing, this isn't sufficient any longer, as it seems.
> Unless you have the source to those libs to re-compile in xHarbour (or
someone has provided equivalent libs/functions)
> then you'll have to stay with Clipper as they won't be compatible.
So, in other words: we can't simply use xHarbour to recompile our app
and link in the existing third-party libs. (This _might_ be the reason
why testing with xHarbour has been discontinued here..)
Best wishes,
Karsten
--
PGP Public Key ID 0x708CD1FE (pgpkeys.pca.dfn.de)
"When the light of day is dead, the spark of night ignites"
|
