Hi Przemek, We currently also use the '()' non-optimization for HB_SYMBOL_UNUSED().
If we can resolve the above, and make it possible to disable the feature using -k switch, I think we are fine with it. If this involves any complexities though, I'd leave it for after RC1. Brgds, Viktor On 2008.06.02., at 16:46, Przemyslaw Czerpak wrote:
2008-06-02 16:46 UTC+0200 Przemyslaw Czerpak (druzus/at/priv.onet.pl) * harbour/include/hbexprb.c ! do not optimize HB_BIAND(), HB_BITOR() and HB_BITXOR() when only one parameter is passed to keep RT error compatibility * use hb_compExprListStrip() to optimize function calls also when parameters are passed in parenthesis, f.e.: ? CHR(65), CHR((65)) It's not Clipper compatible and disabled by -kc switch. Viktor it will interact with some hbtest tests when compile timeoptimization used by Clipper gives different results then RT functionf.e. CHR( ( 256 ) ). Please think if we should keep it. It's important optimization if someone uses constant values or expressions defined in parentheses. best regards Przemek _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
