PC Toledo

Hi,

xHarbour is not my dream anyhow I strongly suggest
that someone who is interesting in keeping this project
alive and having enough knowledge about xHarbour
internals verified recent Luiz modifications.
Otherwise this project will die shortly.
Luiz, it's nothing personal to you but each your recent
modification for macrocompiler introduced new critical
bugs like memory corruptions or GPF traps. You cannot
copy some code from Harbour if you do not fully
understand what Harbour and xHarbour does on different
levels. A lot of internal structures and code in Harbour was
rewritten to eliminate different bad side effects what allowed
to greatly simplify upper level code and increase performance
but now if you try to copy Harbour upper level code without
low level modifications then the results are unpredictable.
Such modification can be done only by someone with realy good
knowledge about [x]Harbour internals. You started with simple
modification with buffer overflow and ended with version which
corrupts readonly memory area.
Here is self contain example which illustrates one of
the problems you introduced:

proc main()
local cVal
cVal := "{|| 1 }"
? cVal
? eval( &cVal ) // GPF on systems with RO memory protection
? cVal // modified value on systems without it
return

Probably Ron can help you verifying your modifications and updating
simplex. Meanwhile I suggest to remove all your recent modifications
from SVN. If you will continue such "minor fixes" then after some
time no one will be able to restore usable xHarbour state without
some global code revert.

best regards,
Przemek

Itamar M. Lins Jr. escreveu:Quando eu digo... o pessoal vem com paus e pedras mas fazer o que né ?

Olá Itamar, por gentileza, poderia postar o Link desta publicação?
Luiz, seria o Luiz Rafael Culik?