On Mon, 09 Mar 2009, Rossine wrote: Hi,
> Because the program below, generates a compilation error: > [CODE] > *#include "fivewin.ch" > #ifdef __HARBOUR__ > #ifndef __XHARBOUR__ > #include "hbcompat.ch" > #endif /* __XHARBOUR__ */ > #endif /* __HARBOUR__ */ > function MAIN > local cTeste := "nVar = 2" > private nVar := 1 > if .not. ( empty( cTeste ) .or. &( cTeste ) ) > ? "NO" > else > ? "OK" > endif > return NIL > [ENDCODE] > Generate this error: > Harbour 1.1.0dev (Rev. 10564) > Copyright (c) 1999-2009, http://www.harbour-project.org/ > Compiling 'hrberr3.prg'... > hrberr3.prg(16) Error E0030 Syntax error "syntax error at ')'" > hrberr3.prg(18) Error E0014 ELSE does not match IF > hrberr3.prg(20) Error E0010 ENDIF does not match IF > 3 errors It's cause by very danger rules used to emulate Harbour bit operators: &, |, ^^ in hbcompat.ch: #translate ( <exp1> | <exp2> ) => ( HB_BITOR( (<exp1>), (<exp2>) ) ) #translate ( <exp1> & <exp2> ) => ( HB_BITAND( (<exp1>), (<exp2>) ) ) #translate ( <exp1> ^^ <exp2> ) => ( HB_BITXOR( (<exp1>), (<exp2>) ) ) I suggest to comment these lines. & has special meaning in Clipper and using it as bit operator in xHarbour creates syntax problems. We cannot replicate exact xHarbour behavior even on compiler level without breaking some valid Clipper code. The above PP rules are simple hacks which can help in some places but also can break some other code just like in your example. If you need bit operators then use HB_BIT* functions. They are optimized by compiler at compile time so you can use them also to initialize static variables. best regards, Przemek _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
