FIle encoding prevents muparserx from compilation about muparserx HOT 6 CLOSED

I can't reproduce this issue with Linux mint/GCC 4.6.3. What platform did this 
happen on? 

latest archlinux - gcc 4.7.2 i think

Unfortunately there is no good answer to this problem. My top priority is 
ensuring the archive is compilable on as many platforms as possible. In this 
case it may actually mean i have to remove the offending code entirely. Here is 
why:

The main development platform is windows 7/VS2010 thats not likely to change 
despite the fact that i do some coding with qt creator. There does not seem to 
be a viable way of making VS2010 save UTF-8 (without signature or BOM) as the 
default. Moreover a quick google search reveals that the microsoft compiler 
cl.exe has issued with UTF-8 when saved without signature. That may be the 
reason why VS2010 does append a signature to each UTF-8 file it saves even if 
it was load without a signature. So much for the failures of VS2010/cl.exe. GCC 
in turn seems to have issued with reading UTF-8 containing signatures as it 
prefers the plain UTF-8 flavor. Whatever i choose i will cause problems on the 
other side of the operating system spectrum. I have no idea why archlinux is 
failing whilst Ubuntu/Linux Mint seem to accept the code. 

I will check this myself yet but if this all is true the only solution i see is 
not defining an operator named "µ" at all and sticking to Codepage 1252.

I changed encoding of files, now it works, checked under linux/windows - visual 
studio/makefile/qt creator -> works.

Recommendation: save newly created files in utf-8 encoding, bom does not matter.

Used tool: recode

I'm not entirely sure whether we've seen the last of this. Files explicitely 
saved in vs2010 as utf-8 are not listed as utf-8 when viewed with notepad++. I 
have still a lot of files listed with ansi coding in the repository. On the 
bright side: VS2010 seems to retain utf-8 when processing a file that is utf-8 
encoded.