Yes, it's bug fix. In VFP8 everything after CHR(13) is ignored in EVALUATE(). IN VFP9 CHR(13) is treated the same way as CHR(10) which generates an error in VFP8.
I'm not sure what you mean about 'execute incomplete code'.

>Run this:
>no errors in VFP8
>

>X=CHR(13)
>=ASC('&X')
>=EVALUATE(["]+m.x+["])
>

>
>A bug fix ?
>Where this bug creates problems?
>One what is sure:
>this slowdonw all the EVALUATE() that I use in order to construct parametric scripts.
>
>But the true issue,
>where exists the possibility to execute incomplete code has been resolved?
>
>No:
>

>x="? 1"+CHR(13)+"? 2"
>&x
>x="trx(1)"+CHR(13)+"trx(2)"
>EVALUATE(x)
>
>PROCEDURE trx(z)
> ? z
>

>
>Fabio