News for hackers. Stuff that matters.
Re:A Developer's Perspective On Porting Games To Linux by blt on Thursday May 08, 2014 @04:57PM (#7717657)
Yes, but that doesn't mean the original developers used them :)

Some developers are shockingly Microsoft-centric...

Re:A Developer's Perspective On Porting Games To Linux by flohofwoe on Thursday May 08, 2014 @05:37PM (#7717858)
Doesn't have to be on purpose, for instance Visual Studio inserts backslashes in autocompleted C/C++ header paths by default (can be set to forward slash in the settings, but default is backslash). The case-insensitive filesystems on Windows and OSX are usually also a problem when moving games with hundred-thousands of source- and asset files over to a Linux build system.
Re:A Developer's Perspective On Porting Games To Linux by scrollaway on Saturday May 10, 2014 @12:11AM (#7724459)
OSX/HFS has case insensitivity? Since when?
Re:A Developer's Perspective On Porting Games To Linux by flohofwoe on Monday May 12, 2014 @03:49PM (#7735018)
I was baffled too but that's like it is by default, on my MBP #include paths don't have to match case, just like on Windows. Or you can do a 'echo blub >bla.txt' followed by a 'echo blob BLA.txt' and there will only be a single file 'bla.txt' which contains the string 'blob'.
Re:A Developer's Perspective On Porting Games To Linux by derekp7 on Thursday May 08, 2014 @11:31PM (#7719170)
I meant they didn't have to use path.join, they could have changed them all to forward slashes and it would still work on both.
Re:A Developer's Perspective On Porting Games To Linux by mhurron on Thursday May 08, 2014 @05:07PM (#7717717)
You mean like DirectX developers? Funny that really.