Fixed this for the next release - it was caused by indexing code thinking that the text inside the comment is the preceding expression
