On 27/09/13 21:13, Jonathan M Davis wrote:
No, it should not be executable. The only time that it makes sense for a .d file to be executable is when it's a script with something like #!/bin/rdmd at the top, which certainly isn't the case for windows.d.
Is testing for correct permissions something that can be included in the auto-tester? Seems likely that it could happen again by accident if someone edits windows.d on Windows (which is probably the most typical place to edit it).
