4 ms·
Having a toplevel src/ (vs. lib/ or test/ etc) is just a convention and I have no problem with that one. The last part of the path is required by the conventio
by darklajid 15y ago
Having a toplevel src/ (vs. lib/ or test/ etc) is just a convention and I have no problem with that one.
The last part of the path is required by the convention of having a unique/meaningful namespace/package name and the language requirements (not sure if I like that or not, C# doesn't have this - sometimes I love that, sometimes I curse when I search for the file that contains a certain class):
- Namespaces have to correspond to folders.
- File names have to correspond to the (first?) public class declared within.
(From memory, I hope I have no _really_ big flaws in there. Haven't touched Java for quite some time)