>Hello to all:
>I discovered something today that I'd like to share with the rest of you, and get your input on how YOU feel it should be handled.
>
>I had a line similar to the following:
>
>do c:\windows\desktop\myprogram.prg with para1, para2, para3, ;
> para4, para5, para6
>
>I moved the program from my local drive to the network, but I wanted to save the previous code, in case I needed to switch back, so I just commented it out, so my code looked like this:
>
>*do c:\windows\desktop\myprogram.prg with para1, para2, para3, ;
>do l:\programs\myprogram.prg with para1, para2, para3, ;
> para4, para5, para6
>
>When FoxPro runs this code, it looks at that first commented line, sees the semi-colon on the end, and then decides that the following line is a continuation of that comment! Although the following lines do not show up as my customized comment coloring in the code, they are parsed as such when the program is written in Binary.
>
>My take on this is that ANYTHING in a commented line should be ignored by a parser/compiler. It is clear that in this case, some of my code was affected by a character contained in a commented line. How do all of YOU feel? Should this semi-colon be treated like all other semi's and be interpreted as "continue this line on the next line.", or do you also feel it should be seen as just any ol' character in a commented out row, and thusly does nothing to the program.
>
>Hope to hear back from some of you.

Paul,

This is an old and known issue. The question is, "How would you indicate the difference to the compiler?" Compiler directive? That would bring about, "Is the view worth the climb?" IMO, no it isn't. The behavior is both known and consistent.