3 ms·
> In codebases that allow out of order definitions, things get wild real quick. Not an issue in C# at all. Get wild in what way?
by naasking 3y ago
> In codebases that allow out of order definitions, things get wild real quick.
Not an issue in C# at all. Get wild in what way?
- WorldMaker 3y agoIt can be an issue in C#. I've seen some mad circular dependencies between files. The file hierarchy doesn't always reflect the namespace hierarchy which sometimes doesn't reflect the actual code dependencies hardly at all and untangling the messes that result from that can be a big deal. I'm not sure a project gets into that state "real quick", but it remains something that projects can do over time, sometimes without realizing it, especially when a DI abstraction makes it even less obvious how circular a project's dependencies really are.
- naasking 3y agoI'm not sure why those things are necessarily a problem, particularly when with IDEs or at least editors that can parse a language's symbols. We're not programming the dark ages. Do you have a specific example of why these are an issue?
- xupybd 3y agoI think wild real quick might be a bit extreme but cyclomatic complexity[1] is a source of unnecessary complexity in software. While not a problem per se, all unnecessary complexity adds up. Leading to the eventual death of the project[2] [1] https://en.wikipedia.org/wiki/Cyclomatic_complexity [2] https://en.wikipedia.org/wiki/Software_Peter_principle