>
>You misunderstood this -
>it can save the files with or without the EOF marker in the end,
> which is for compatibility with whatever other software the user is using, which may need the EOF marker to work properly. But if the EOF marker is found in the source,
> Visual FoxPro will respect it, not ignore it.
>
>
>This is not true.
>
>Read my Message #897948
>
>Dragan, this is a VFP parser problem, correlate with the strings, not with the file.

I've tried putting chr(26) in comments (by typing alt+026) and it is ignored. Seems to be VFP is ignoring anything in a comment - a comment is parsed for end of line and nothing else matters.

But it's caught anywhere else - if it's a part of a string literal, it's end of file before end of string, therefore an error. If it's on a line for itself, it's again an EOF, and lines after this aren't even considered by compiler. You can put megabytes of anything after an eof marker, and it will be ignored.

So I stand corrected that it ignores eof markers in comments - I didn't know that. But then, I think even that was so for a number of versions. I don't think this is a bug, because there's no expected behavior that it differs from.