Bug 6592 – di header file created even if errors occur

Generating a di file from --- module test; import std.foo; --- via "dmd -H -o- test.d" generates errors: test.d(2): Error: module foo is in file 'std\foo.d' which cannot be read but still creates the test.di file --- // D import file generated from 'test.d' module test; import std.foo; --- This can confuse the hell out of any make like build tool. BTW: that is also the reason why building druntime works on windows if run twice, it reports an error only the first time (this uses posix.mak on windows, the win32.mak just misses un.di from the list of imports): ../dmd/src/dmd -m32 -c -d -o- -Isrc -Iimport -Hfimport/core/sys/posix/sys/un.di src/core/sys/posix/sys/un.d DMD v2.055 DEBUG src\core\sys\posix\sys\un.d(17): Error: import sa_family_t not found src\core\sys\posix\sys\un.d(17): Error: alias core.sys.posix.sys.un.sa_family_t recursive alias declaration

The same is true for object files, although Walter said he wants them around to be able to inspect the output. Maybe this applies to .di files as well. (personally I disagree with such a viewpoint, if something crashed or emitted an error the compiler source should be inspected, not its corrupted output).

@cristiancreteanu updated dlang/dmd pull request #10635 "Issue6592 - di header file created even if errors occur" fixing this issue: - Fix Issue 6592 - di header file created even if errors occur https://github.com/dlang/dmd/pull/10635

dlang/dmd pull request #10635 "Issue6592 - di header file created even if errors occur" was merged into master: - 4f83b1888b209f7963fa7a778739656662e81df0 by Cristian Creteanu: Fix Issue 6592 - di header file created even if errors occur https://github.com/dlang/dmd/pull/10635