I'm running 10.5.5, and I'm getting totally different results. Here is what I did:
In the Set Variable command, I clicked on Specify and entered:
and I get "The specified table cannot be found"
Since there are quotes in the string, I instead use:
"/* I am a " & "\"" & "comment." & "\"" & "/*"
This works properly.
I'm obviously missing a step here.
When you type the comment, do not surround it with quotes.
I.e.: /* like "this" */
not: "/* like "this" */"
Sorry... My bad. I wasn't thinking of this as a comment per se, but as a calculation.
I understand now, and I understand why it does this, so I have forwarded your entire post to our Software Quality Assurance (Testing) department asking for this to be changed.
Thanks for taking the time to report this.
Thanks TSGal. There are so many times when I just blow by a FileMaker annoyance, thinking "surely someone has reported this." But as the engineers remind us at DevCon, the more people report something, the higher priority it gets.
I must say I am loving this new forum. What a refreshing change to see FileMaker feedback and bug reports out in the open, and to have your reports acknowledged and discussed.
Does it help get bugs fixed faster when more people chime in that something like this is a very annoying problem? The original report was about 9.0v3, but this is still a problem in 10.0v3 (Windows XP). And I'll just add that not only does everything get escaped, but all line spacing becomes FileMaker return characters, so that it is all just one big run-on sentence of a calc, which makes the commented calc difficult to read AND incorrect.
For example, this:
a = "Hello ";
b = "World"];
a & b
"/*¶Let([¶a = \"Hello \"; ¶b = \"World\"]; ¶¶a & b¶)¶*/"
Thank you for your post.
Unfortunately, I I don't know what occurs when "more people chime in". In any case, I have attached your post to the original case.