4 ms·
Eh, any sufficiently large or complex codebases will get ridiculously long names at some point. Here are some from a famous C API (Windows): CoMarshalInter
by thu2111 6y ago
Eh, any sufficiently large or complex codebases will get ridiculously long names at some point. Here are some from a famous C API (Windows):
CoMarshalInterThreadInterfaceInStream
D3D12_GPU_BASED_VALIDATION_SHADER_PATCH_MODE_UNGUARDED_VALIDATION
RtlWriteDecodedUcsDataIntoSmartLBlobUcsWritingContext
Or how about:
GtkColorSelectionChangePaletteWithScreenFunc
The alternative is things having names that aren't actually descriptive at all, which is not clearly better.
- madia_leva 6y agoOr have a good package system... If you use a language with import with aliases, you don't need all that noise.
- thu2111 6y agoJava has such a system but people write long class names anyway, because people don't like to have too many types with identical names distinguished only by namespace. You can do it but it's a bit questionable to what extent you should.