On Mon, 02 Jun 2008, Szakáts Viktor wrote: Hi Viktor,
> >Clipper does not make any optimizations for macro compiled > >code so it gives correct results executing RT functions or > >evaluating PCODE. We are making the optimizations but for > >macro compiler Harbour calculates correct results so there > >is not problem here. > Even better. So I expect not too many ppl having > Chr( 1024 ) and "" $ "string" in real life code, since > the expressions are pointless, they are side cases > (invalid or close to invalid input) by themselves, > someone using such expressions with _full literals_ > is even more pointless. So besides inspecting these > in a lab, like some strange viruses, they serve no > purpose, and I don't expect finding them in too much > real world code. I can quite easy change it and make -kc strictly Clipper compatible. For -kh we will not replicate the bugs in $ / CHR() / AT() optimization. I can also add separate switch to control it but I do not know if it's necessary. > [ NOTE: Clipper '87 had these right, and I bet > - but I cannot try right now - the rest of Clipper > compiler has this right too. ] Probably S87 does not have compile time optimizations. best regards, Przemek _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
