Bug 3408 – compiler asks for object.d when it really expects object.di

If a user has a problem with their path setup (such as a missing sc.ini), they will likely see this error message: object.d: Error: module object cannot read file 'object.d' Since DMD2 doesn't come with an object.d (but rather object.di), the error message should reflect that. Perhaps it should be: object.d[i]: Error: module object cannot read file 'object.d[i]' This error message could especially be frustrating for a new user who might be having difficulty setting up DMD.

Actually, I'd argue in this particular instance, since we know that the compiler failing to find object.d means that the user doesn't have their paths set up correctly (probably due to a bad dmd.conf or a the wrong one being found first), it would be beneficial to give a much more specific error that indicated that dmd couldn't find the standard libraries because the paths or dmd.conf were not set up correctly. Also, it would be very useful for the first time user if this problem were specifically mentioned on the installation page for dmd with instructions as to the likely causes (missing dmd.conf, poorly configured dmd.conf, find wrong dmd.conf first, etc). It would make it much friendlier for people to try and install D for the first time - particularly since this is a fairly common problem.

*** This issue has been marked as a duplicate of issue 7192 ***