This content has been marked as final. Show 3 replies
Thanks for reporting this issue. I have logged the issue into our bug tracking system so that it can be tracked and fixed in future releases.
It exists in prior versions of Apex, too. I'm looking at it in the file from 4.2.2, same line.