Quote Originally Posted by jimblumberg View Post
I sincerely hope not. IMO, windows.h is an abomination since it is from the "throw in every thing, including the kitchen sink" mentality of programming. Realize that #including that header can cause almost every windows API header to be #included. On other operating systems they prefer you to only #include necessary includes, not every #include under the sun. Remember that #including unnecessary #include files can cause increases in compile times.
That is a good point; I have gotten into the habit of looking up the actual header the functions I'm using are in, so I don't think I've done <windows.h> in a long time.

And to go back a bit to one of the original questions; the prefix-with-a-dot method hides a file from "normal" directory listings (although there is a flag to show them, just as "hidden" files can be seen via some clicking), but in general on a *nix system a program will have the same filesystem privileges as the person who runs the program, so if your program wants to be able to edit a file the user has to also be able to edit that file. Making the structure of the file opaque can't prevent a user from corrupting the file, but at least it's possible that the edit they make will just corrupt the file rather than change it to something valid-but-different.