3 ms·
Something I hate about about c is that you don't know where the hell somefunc() came from. Some languages have foo.somefunc() which I think works quite well al
by benj111 4y ago
Something I hate about about c is that you don't know where the hell somefunc() came from.
Some languages have foo.somefunc() which I think works quite well although iffooisrealllylong.function() is a risk.
I suppose this gets you the best of both worlds.
Although using let does seem a bit weird to me. It seems conceptually misleading.
- mdaniel 4y ago> Something I hate about about c is that you don't know where the hell somefunc() came from. I think you mean something you hate about not using an IDE with the language. One can do `from onoz import *` in python and Java to have a similar "wait, where did do_magic() come from?" experience, and then Scala will see your wildcard import and raise you implicit methods, which can die in a raging fire tornado
- benj111 4y ago>I think you mean something you hate about not using an IDE with the language Well it's a 'feature' of the language so the criticism still stands. Ides could solve a lot of language warts but we still rightfully criticise the language for the warts. C's lack of memory safety could be solved by good programming practices, but we still criticise c for the lack of memory safety.
- mytailorisrich 4y agoThis is true that there is no language feature to enforce this. But this can be worked around by enforcing naming functions with adequate prefixes, which is a very common approach, if not a best practice.