4 ms·
No need for insinuations, that's not a point of contention. If you look past the book, and directly at the STL, you'll find a common example: the "fmt" library
by croshan 8y ago
No need for insinuations, that's not a point of contention.
If you look past the book, and directly at the STL, you'll find a common example: the "fmt" library, shortened to save three letters. Or compare the verbosity of these two examples from language docs, and the length and descriptiveness of variable names in them: https://docs.oracle.com/javase/tutorial/essential/io/cl.html https://docs.oracle.com/javase/tutorial/essential/io/cl.html to https://golang.org/pkg/bufio/#example_Scanner_emptyFinalToken https://golang.org/pkg/bufio/#example_Scanner_emptyFinalToke...
I agree, it's a great language. These naming conventions are part of its developers and community.
- entity345 8y agoNaming conventions are part of your own practices and processes. There is no issue with having short names to describe well-known entities part of the language, or trivial code. Your example from pkg.bufio is trivial and but still the variables names are meaningful. There is a difference between clearly and meaningful, and verbose. Your example from Java is not very different. I feel that the point is not being understood here.