2013-09-16 11:25 UTC+0200 Przemyslaw Czerpak (druzus/at/poczta.onet.pl)
* doc/cmpopt.txt
* doc/xhb-diff.txt
* typos
* src/rtl/hbsocket.c
* simplified hb_socketSelect() code
* src/rtl/mtran.c
! updated HB_TRACE message
This commit is contained in:
@@ -63,7 +63,7 @@ arguments are well known and can be calculated at compile time:
|
||||
// can contain '&' character. Harbour checks
|
||||
// if concatenation can change existing valid
|
||||
// macro name or ignore '&' when -kM compiler
|
||||
// switch which disable macro substitution
|
||||
// switch which disables macro substitution
|
||||
// is used
|
||||
<nConst1> - <nConst2> => <nConst>
|
||||
<dConst1> - <dConst2> => <dConst>
|
||||
@@ -73,7 +73,7 @@ arguments are well known and can be calculated at compile time:
|
||||
// can contain '&' character. Harbour checks
|
||||
// if concatenation can change existing valid
|
||||
// macro name or ignore '&' when -kM compiler
|
||||
// switch which disable macro substitution
|
||||
// switch which disables macro substitution
|
||||
// is used
|
||||
<nConst1> * <nConst2> => <nConst>
|
||||
<nConst1> / <nConst2> => <nConst> // Clipper optimize only integers
|
||||
@@ -85,7 +85,7 @@ arguments are well known and can be calculated at compile time:
|
||||
// can contain '&' character. Harbour checks
|
||||
// if after '&' is potentially valid macro
|
||||
// name or ignore '&' when -kM compiler switch
|
||||
// which disable macro substitution is used
|
||||
// which disables macro substitution is used
|
||||
<lConst1> == <lConst2> => <lConst>
|
||||
<nConst1> == <nConst2> => <lConst>
|
||||
<dConst1> == <dConst2> => <lConst>
|
||||
@@ -94,7 +94,7 @@ arguments are well known and can be calculated at compile time:
|
||||
// can contain '&' character. Harbour checks
|
||||
// if after '&' is potentially valid macro
|
||||
// name or ignore '&' when -kM compiler switch
|
||||
// which disable macro substitution is used
|
||||
// which disables macro substitution is used
|
||||
|
||||
NIL == <xConst> => <lConst>
|
||||
<xConst> == NIL => <lConst>
|
||||
|
||||
@@ -10,7 +10,7 @@ It describes status of both compiler at the end of October 2009:
|
||||
|
||||
Przemek,
|
||||
|
||||
(Przemyslaw Czerpak, druzus/at/acn.waw.pl)
|
||||
(Przemyslaw Czerpak, druzus /at/ priv.onet.pl)
|
||||
|
||||
|
||||
|
||||
@@ -742,12 +742,12 @@ If it's possible then for macrocodeblocks Harbour compiler tries to
|
||||
generate early eval code in which macros are expanded when codeblock
|
||||
is created. Otherwise macros are expanded each time codeblock is
|
||||
evaluated.
|
||||
xHarbour has also similar extension but limited to only to macro
|
||||
variables and it works only if other macros are not used in the
|
||||
same expression. When more complicated examples are create xHarbour
|
||||
compiler generates broken code which generate RTE or GPF during
|
||||
execution. It also does not support codeblocks which contain mixed
|
||||
macros and refuse to compile such code.
|
||||
xHarbour has also similar extension but limited to macro variables
|
||||
and it works only if other macros are not used in the same expression.
|
||||
When more complicated examples are created xHarbour compiler generates
|
||||
broken code which causes RTE or GPF during execution. It also does not
|
||||
support codeblocks which contain mixed macros and refuse to compile
|
||||
such code.
|
||||
|
||||
This example illustrates macros with declared symbols.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user