4 ms·
I must be one of the few that like the header/code separation. When dealing with plain text, I get a more concise view of what is going, as well as a view of w
by rileymat2 9y ago
I must be one of the few that like the header/code separation. When dealing with plain text, I get a more concise view of what is going, as well as a view of what should be used by other modules.
- s_ngularity 9y agoThe problem with the separation is mainly with making changes to code, not with reading the code as it currently exists. This problem is avoided at no cost in Go, where an external tool can be used to get the same concise view of all of the function types that you like, without needing to manually create and update header files.
- nixpulvis 9y agoWriting code takes effectively no time, reading and reasoning is the primary concern (for me anyway).
- asfasgasg 9y agoMy first question would be: how much experience do you have with other languages? Because C and C++ are the only two major languages that have this separation, and everybody else seems to get on fine without it. If you're knowledgeable about other languages, then fair enough, preferences vary. If not, I ask you to consider the possibility that you only like it because it's familiar.
- rileymat2 9y agoI have been programming for 20 years. C++/Python/JavaScript/Visual Basic/Objective C/Java. Most of my work these days is in JavaScript (Node). I agree it is annoying to write, but I find well documented headers to be more usable than the other environments, if the project is large enough that I cannot read everything.