Executable permission bit on Windows about filesystem

[pdimov]

equal_extension does match mixed case.

Unix shell scripts can't be directly run with fork exec so I'm not sure if the CreateProcess analogy holds. From a C++ viewpoint, executables are those that can be run with std::system so PATHEXT would probably be more appropriate.

[Lastique]

I don't think PATHEXT is applicable as it contains extensions of seemingly non-executable files. On my system it lists:

.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC

I don't think you are supposed to run JavaScript from command line, for instance. My understanding is that it is the extensions system shell automatically adds to a file name as it tries to find it in some contexts. That context might not be limited to just executing it.

Executable bit on Windows is a best effort emulation, and I agree with Peter in that it is not tied to a specific API. An executable file is something that can be run from shell command line. Personally, though, I would rather remove that code and not treat anything as executable.