Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Really frustrated by the behavior
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Divers
Thread ID:
00620452
Message ID:
00620719
Vues:
13
>>>>I disagree with you. The meaning of ';' shouldn't change for comment lines but the code coloring should be fixed to show all comment lines in proper color.
>>>
>>>Sergey,
>>>
>>>While I agree with you that it would be nice, I think it would be terribly difficult to implement. The problem is that the editor simply works one line or even keystroke at a time and therefore is unaware of the semi-colon at the end of a previous line.
>>
>>First, we don't know that for sure. Second, you wouldn't reject a user request just because it is difficult to implement, would you?
>
>Well, I agree that we don't absolutely, positively, 100% sure know that this is the case. However, given the behavior of the editor, I think it's a perfectly reasonable and rational hypothesis. I do think it would be nice if someone from Microsoft (Mike Stewart, Ken Levy, Randy Brown, Calvin Hsia, John Koziol, etc.) would step in here and either confirm or deny it.
>
>What we do know for sure is that VFP doesn't do real-time syntaxing and compilation. If it did, we wouldn't see some of the compile-time syntax errors that sometimes appear when we have mis-matches (parenthises, WITH/ENDWITH, etc.) Other products support it. If it did, I think that the behavior could be dealt with more easily.
>
>This behavior isn't exactly new. It's been with us (and been complained about) since syntax coloring first appeared. While it's a nice feature and makes our development easier, I would think that there might be other areas of more significance that could be worked on. FWIW, this behavior with the semi-colon has been the case even before syntax coloring appeared.
>
>As I mentioned in my other post, there are other instances where syntax coloring doesn't display as it should, yet no one seems to mind those as much as this one.

I personally never cared about this limitation much. Ii happened that it came to my attention before it could crawl out and bite me. :)
Since then I just never use semi-colon in comments and if I comment out the piece of code with semi-colons I always leave an empty line between the comment and the following code.
Nick Neklioudov
Universal Thread Consultant
3 times Microsoft MVP - Visual FoxPro

"I have not failed. I've just found 10,000 ways that don't work." - Thomas Edison
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform