[lazarus] Can't cycle new compiler

[Peter Vreman]

> > But it works now again... Tomorrow i want to see the assert's :)
>
>It will work but it does still have one quirk. If uTrace has {$H+}
>declared the const Msg isn't handled correctly. The length character for
>the message string is also printed at the front of the string. If {$H+}
>is declared in uTrace then when the complete uTrace code is used it
>blows up. It doesn't really need {$H+} but this still might cause some
>problems someplace. Oh yeah the unit that was setting the Assert line
>also did NOT have {$H+} set so maybe that is where the confusion comes
>in. Just something else to check.  :-)
The {$H+} in the unit that calls the assert() is not important, the string 
is already automaticly converted to shortstring. You only need to declare 
your new assertproc with 'shortstring' instead of 'string', then the $H+ 
doesn't matter anymore. Maybe we need to declare assertproc with a procvar 
instead of only a pointer, which is again one of borlands strange decissions.