Comment by Geoffrey Wiseman (JIRA)

I took a quick look at `Lexer.cpp`. I think I can see the problem.

Assuming you allow nested slash-star comments, which the lexer seems to allow, I am not sure how you're supposed to decide whether or not "//*/" is meant to open or close a comment. In the absence of any other information, I think it should probably do what it's already doing: assuming that the first valid interpretation – that of opening a comment – is the right one.

Did you have another heuristic in mind for how it should decide?

geoffrey.wiseman (JIRA User) Good point, it's nonobvious what the right interpretation is here. Possibly, when lexing a nested /*, we could look ahead to see if there's a / immediately after the * and favor the */ interpretation.

Comment by Geoffrey Wiseman (JIRA)

In which case the lexer would prefer /* at the start and */ thereafter.

These would be legit:

/*/ comment /*/
/*/ comment /*/ code /*/ comment /*/

Granted, almost all of these scenarios are edge cases, and will come up infrequently enough that it's probably not THAT big a deal. Your suggestion doesn't seem complicated, and I can't think of a really ugly counter-example that seems to suggest the it's a problem. I'll give this a spin.

Resetting assignee on all Starter Bugs not modified since 2018.