Stupid bug with 4.6.2f?

It seems the new compiler doesn't like it when you have objects in the scene that start with an integer in their name. I have an enemy called "4hitter" because it does 4 hits...
Up to and including 4.6.1p5, it compiled with no issues (and in fact tested it in 64bits on an iphone6).
Then today i downloaded the 4.6.2 version and Xcode started to show up to 80ish errors all in cpp files with a word that sounded like it wasn't expecting that. Can't remember it and stupid me didn't take a note. But all errors pointed to the object that had that name. So i just renamed it to FourHitter and everything is fine.
Again, it worked great before! Unity isn't giving out any errors on "4hitter", but with 4.6.2, Xcode farts everything when it's named like that.

 

Nice find on the bug, maybe a quick fix, I agree please report this asap so we can solve in 4.6.2 patch 1 for thursday next week if Unity devs are quick!

 

HEY! HEY Listen!
I made a script and named it 4_6UIMessageParentEnable, (perhaps it is a bad habit).
Mono then took that "4" as a reserved word. It highlighted it the same as "false" or "null" and the like, as if it's a number, not the name of something else. It wasn't doing it before.
Could this be related to the bug? I don't know how to update the initial bug report.

Unless my eyes are just ruined and it was doing it before.

 

You can reply to the email confirmation to append comments to your bug report.

 

Ah yeah thx. It even said so at the confirmation email i think. Wish there was a thumbs up icon

 

btw, it's pretty normal not to be able to use numbers at the start of a file/class/function/namespace.

http://stackoverflow.com/questions/6919190/can-i-name-a-c-sharp-namespace-starting-with-a-number

 

Thing is, it was fine before 4.6.2. The object may very well be 4-5 months old in that state.
And there are other objects that start with a number, but it only does that with a "4". And unity lets it pass fine, it works with Android, but not with iOS.