Timeline for Splitting into files - how much splitting?
Current License: CC BY-SA 2.5
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 9, 2010 at 21:28 | comment | added | Mike Strobel | Well, that really depends on the language, but yes, it could certainly have that effect. It's not really an issue for me, as I develop primarily in C# (no file-by-file compilation), but it could be problematic in C++ and other languages. As always, there are language-specific factors to consider, and that would be one of them :). | |
| Aug 9, 2010 at 21:00 | comment | added | PrettyPrincessKitty FS | Doesn't grouping your enums mean changing a single value would cause a recompile of every file that uses an enum in that namespace? | |
| Aug 9, 2010 at 19:31 | vote | accept | PrettyPrincessKitty FS | ||
| Aug 9, 2010 at 19:09 | comment | added | Mike Strobel | Agreed. Complexity of your types should definitely be a factor. If your language supports partial classes (or if member implementations can be organized similarly to C++), then I would even recommend breaking up particularly complex types into multiple files. For example, if there's a (large) interface that your class must implement, but the code is fairly generic and not terribly relevant to the rest, you could break that code out into a separate file/partial class. For enum types, I think you could get away with placing all enums for a given namespace within a single file. | |
| Aug 9, 2010 at 16:29 | history | edited | Ricket | CC BY-SA 2.5 |
deleted 8 characters in body
|
| Aug 9, 2010 at 16:20 | history | answered | Ricket | CC BY-SA 2.5 |