Analysis tripped up over UTF-8 files with BOM

[mpaluchowski]

A UTF-8-encoded file with the BOM adds a number of bogus issues to the analysis result, starting with:

<issue severity="ERROR" id="PARSE_ERROR" message="PARSE_ERROR" category="CFLint" abbrev="PE">
  <location file="foo.cfc" fileName="foo.cfc" function="" column="1" line="1" message="Unable to parse" variable="">
    <Expression><![CDATA[token recognition error at: '»']]></Expression>
  </location>
</issue>

[ryaneberly]

I've seen that error once or twice. Thanks for the explanation.

…

On Tue, Mar 7, 2017 at 8:20 AM, Michał Paluchowski ***@***.*** > wrote: A UTF-8-encoded file *with* the BOM adds a number of bogus issues to the analysis result, starting with: <issue severity="ERROR" id="PARSE_ERROR" message="PARSE_ERROR" category="CFLint" abbrev="PE"> <location file="foo.cfc" fileName="foo.cfc" function="" column="1" line="1" message="Unable to parse" variable=""> <Expression><![CDATA[token recognition error at: '»']]></Expression> </location> </issue> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#250>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFtZu868-judONfSqvvHEwsqhocRfLiPks5rjVmTgaJpZM4MVeGU> .