Ron Pinkas wrote:
> [..]
> 1. Have you tried using Memory( -1 ) to explicitly activate Clipper's
> Garbage Collector?
Has no visible effect.
> 2. I'd strongly suggest a recompile of your app under xHarbour, which is
> practically 100% Clipper compatible, and does not suffer from these
memory
> size limitations.
This has already been discussed (and, as far as I know, tested).
However, a colleague did some experimentation with xHarbour and ended up
with an error message from an application compiled with xHarbour. I was
not involved, so unfortunately I can't tell any details. For some
reasons, further tests have been discontinued then.
As far as I see the entire problem, there is nearly no alternative than
again try and recompile our apps with xHarbour. What I'd be interested
in then, is: are all of our source codes and third-party libs compatible
(Clipper 5.2b, Class(y) 2.4b, Clip-4-Win 2, Funcky, Novlib, SixNSX 3,
ADS 6.11/7, TCS4Win; hope, I mentioned all..), and what effort would be
necessary recompiling with xHarbour (changes to source code, linker,
build scripts)?
Best wishes,
Karsten
--
PGP Public Key ID 0x708CD1FE (pgpkeys.pca.dfn.de)
"When the light of day is dead, the spark of night ignites"
|
