Harbour stable release (2.2.0)

"Viktor Szakáts" <harbour.01@syenar.hu> Jun 16 12:41PM +0200 ^

Hi All,

I plan to make stable release till the end of July.

I'd like to ask everyone to start doing tests using
current SVN and report build and user-level bugs
on all platforms. Use default build settings for these
tests, and try using latest versions of 3rd party
libs and tools. Also test bcc55.

Feature freeze: I'd also seriously ask everyone to
_not commit any new features_ till the release is
done, but instead focus on reviewing and fixing
anything available in current SVN. Hold off any
fixes which may seem prone to regression.

The version of the release will be 2.2.0. (2.1.x is
too worn by now).

The Windows unified binary will feature libs for
mingw, mingw64, msvc, msvc64, mscvarm and bcc55.
(watcom dos/os2/linux and pocc will be left out
compared to prev build)

When we're clean, I'll do the source release,
tagging and windows unified release, and I ask
contributors to create OS/2, Linux, OS X, *BSD
builds as before.

Focus on these when testing. Thank you.

Viktor

Harbour/xharbour Diff : 11/57 -MACRO MESSAGES by Przemyslaw Czerpak

###    MACRO MESSAGES    ###
============================
Both compilers Harbour and xHarbour supports macros as messages.
Clipper does not. This example shows such macro messages usage:

      proc main()
         memvar var
         local o := errorNew(), msg := "cargo"
         private var := "CAR"

         o:&msg := ""
         o:&( upper( msg ) ) += ""
         ? o:&var.go

Users who want to test it in xHarbour should change:
      o:&( upper( msg ) ) += ""
to:
      o:&( upper( msg ) ) := o:&( upper( msg ) ) + ""
because using macro messages with = operators or pre/post
incrementation/decrementation causes that xHarbour compiler GPFs during
compilation.