
29 Mar
2006
29 Mar
'06
8:29 p.m.
On 3/29/06, Foster Brereton <fosterb.boost@gmail.com> wrote:
The reason this is a problem is because our projects have warnings-as-errors turned on. We are not interested in disabling warnings-as-errors to mitigate the issue because of the far-reaching side effects of such a change.
Has anyone else seen this problem? Are there other potential fixes other than removing all high-ASCII characters from the source files?
Disabling that particular warning?