>SNIP
>> It does look like a bug - or simply, a situation that the compiler can't cope with.
>
>And the second wouldn't be a "bug"????
In this case, probably it is. Although some "compiler situations" have their logical explanations. For instance, generating an error for
seek(Expression)
without the "=" sign at the beginning, because of a possible confusion between the seek command, and the seek function.
Or an expression being too complex - the fact that the compiler has certain limitations isn't necessarily a bug.
In the present case, as long as I don't receive an explanation to the effect that it is quite logical that an error message appears, I would consider it a bug.
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
