I can replicate this issue on my Windows XP system, but I also have some additional observations:
- The first /* inside the quotes is not a factor. I can get the same results whether I include it or not.
- Putting */ in the comment after // does not cause a problem.
- It only occurs when /* is included inside a comment started with //. Thus, the import process apparently fails to treat /* as literal text, but tries to interpret it at the start of a comment and thus produces an invalid expression and error.
- Putting /* inside an existing comment seems nonsensical in most cases
I agree that it's a bug, but not one that's likely to be encountered in most situations.
Thank you for posting.
My tests produced the same results as PhilModJunk's tests (thanks, PhilModJunk!) on both Windows and OS X. I've forwarded this thread to our Development and Quality Assurance departments for further investigation.