ID:108025
 
Applies to:DM Language
Status: Open

Issue hasn't been assigned a status value.
Would it be possible to have some more specific debugging for runtime errors? For example, say I have two files:

base_game/+declaration.dm
players/+declaration.dm

..and I get an error in some proc in players/+declaration.dm, would it be possible for the runtime error to say "runtime error: foo at line 97 in players/+declaration.dm" (as opposed to just +declaration.dm)? It looks like this is possible since the .dme keeps track of all of the files, but I don't know if it's possible to tell them things related to their folders, too.
No, it doesn't tell you the folder, just the file. If I have two files of the same name, for whatever reason, they won't report which folder they're in, even though it's often simple to figure out, it may not always be the case.
When DEBUG is defined, include full (relative to project directory) paths to code files, rather than just the file name itself.

In our codebase, we have a layout like this:

mob\living\carbon\human\hud.dm
mob\living\carbon\monkey\hud.dm
mob\living\silicon\ai\hud.dm

When an error occurs, we have to investigate which file it actually was. Having full paths would improve error information. :)
In response to Slurm (#3)
This would be very helpful.

I've ran into this very same issue with a bug which was in code/social/party.dm but I kept checking code/HUD/party.dm.
In response to Slurm (#3)