Where are the the comments in dmd?

[Ola Fosheim Grøstad]

On Monday, 3 May 2021 at 13:17:29 UTC, Blatnik wrote:
> Honestly another difficult thing to get is the file names 
> themselves.
>
> `ty.d`, `ph2.d`, `mars.d`, `melf.d`, `fp.d`, `ee.d`, `e2ir.d`, 
> `eh.d`, `el.d`, I could go on and on hahaha.
>
> I get that it's probably nice to not have to type a lot in the 
> import statements when you actually know what the all the files 
> are after a year of hacking, but it's really hard to guess 
> where something is.

Yes, you have to start in one end and focus on that end, then 
slowly move to other files to get the structure. Directories 
would help, better names would help. Doesn't take much time to do 
either, not sure why nobody has done it yet?


> Also, a lot of comments are rather useless.

I am not sure how much comments will help (me). I have more an 
issue with long files, and basic structure.

Grepping and inserting print-statements to see what the flow 
actually is seems to be the best way to get an intuitive 
understanding of the structure with the current sourcebase.

(I am not talking about the DMD backend... I have no intention of 
looking at that one.).


> There's basically no way to know what something is for without 
> doing a grep for it across the entire codebase..

I haven't had many problems related to "what", but I keep to run 
into the problem of "where???". :-D

But, yes, grep + print-statements... You better like puzzles.