On 15/04/13 15:06, Hans wrote:

> It may be present in other versions too, I haven't tested that..

...code snipped...

> Returns:
>
> A = 1 and B = 11 instead of giving some error by the parser.
> Can be difficult to find this coding error.

That's expected behaviour, comments can cover line-breaks, all it looks
for is the next occurrence of '*/'

Similarly, you can't nestle comments, e.g.

/* outer /* inner */ outer */

...fails; the "outer */" is passed on instead of skipped.

Using an editor that can highlight syntax is helpful for spotting this.

Scott