More Updates From Aspyr Media On Linux & Mac Progress For Civilization Beyond Earth

>working around issues like case sensitivity on the Linux side for filenames

What's more weird is the fact that programmers didn't use everything in lowercase from the start. They are pretty used to case sensitivity :O

Usually is not programmers fault, but artists, as they work on windows machines with horrendous software like 3dsmax and ps, usually they don't care filenames, if they did, world would be a better place.

Liam is back ! :D

I'm going to hold off purchasing this game since it will probably be like Civ 5 in that it kinda needs the expansion packs to be really good. Though technically I probably shouldn't buy this game (even though I'll most likely still get it) since it will ruin all my productivity which would be bad since I'm in college.

Also glad to have ya back Liam!

Quoting: Ignis>working around issues like case sensitivity on the Linux side for filenames

What's more weird is the fact that programmers didn't use everything in lowercase from the start. They are pretty used to case sensitivity :O

When I started programing on Linux I hated case sensitivity and I still hate it :). This was one of the many windows features I liked.

Quoting: ImantsWhen I started programing on Linux I hated case sensitivity and I still hate it :). This was one of the many windows features I liked.

I have a question and maybe you can answer it...
Why would anybody, if the OS forces him or not, would use different casing on disc and in code in the first place? I a) automatically use a pattern, like camel casing, pascal casing, all small, all large or whatever, and b) am probably to lazy most times to type it twice, so I'd copy and paste the file name. Both ways should ensure consistent casing quite naturally...

Imagine you know perfectly where your header is. You include it without using any completion. It works on Windows, but you may have missed a capital letter somewhere. That's for programming.

Then for the data made by the artists, on top on the fact that there are thousands of files, consider that the name could have changed during the process. An artist could have missed a capital letter and add it back later, but the code doesn't know, and since it still works in Windows, no one cares.

If you know you'll code for a case sensitive OS, it's eventually easier to use small letters and underscores ('_') all the time.

Quoting: GuestI have had these issues while porting a game to Linux and honestly it’s a pain. Now, if a game that needs porting has many wrongly-cased files, I’d probably write a code layer to remove the filesystem’s case-sensivity and be done with it.

I wonder if there is *any* point in having case-sensivity in a file system. I have never needed it and it has always been a nuisance.

I wonder if there's *any* point in being able to put spaces in a file names. Or hyphens, or periods, or the letters x y and z.
/sarcasm

I just don't understand how can an actual programmer think like you. You must obviously know that each character is based on an ascii value assigned in a table of characters, and character A has a different value than character a, and from point of the view of the computer they will always be two completely unrelated things, that just we happen to see some superficial connection between. You have to go out of your way to remove case sensitivity from software. Why do that, when you are removing functionality that way?

Not to mention that when I code, I use case sensitivity with a meaning a lot of the time. Single minor case letters are usually minor variables, like a loop counter or such. All upper case are usually constants of sorts. If I use "BUFFER" I know I am thinking of it as a constant I have set somewhere, and "buffer" would be just a variable, and if I have the variable doesn't exist, the compiler complains, instead of using the constant I forgot to have there.

Quoting: GuestYou’re missing the point. Case-insensivity does not mean you can’t include both upper and lower case letters in your file names.

I'd consider neither case sensitive file names nor case insensitive file names an important feature. People probably don't want to use file names only differing by case. On the other hand, I don't understand why OS/file system writers should be burdened by comparing file insensitive nor why people would _want_ to call a file by another casing that it really has got intentionally (I do understand the accidential case better now, though).

Using and comparing the same ASCII/UTF/whatever numbers should IMHO be the most natural way for every programmer (whatever system he prefers).

Quoting: GuestI have had these issues while porting a game to Linux and honestly it’s a pain. Now, if a game that needs porting has many wrongly-cased files, I’d probably write a code layer to remove the filesystem’s case-sensivity and be done with it.

I wonder if there is *any* point in having case-sensivity in a file system. I have never needed it and it has always been a nuisance.

Yes I did not see in case sensitive file system any point as only that programmers where lazy implementing it. Because it is much assayer to just compare byte by byte. The idea that you can have two files with same name but different case semis ridiculous to me. And it becomes such a bother when you are working in team and others are working in windows. I always tough that it is one of cons for Linux.