3 ms·
Couldn’t agree more. Every time I need to write/read C I’m forced to refer to some documentation just to recall what the right syntax is depending on whether or
by voidhorse 5y ago
Couldn’t agree more. Every time I need to write/read C I’m forced to refer to some documentation just to recall what the right syntax is depending on whether or not I’m declaring or using pointers.
I think go is a good example on how to turn “cleverness” into clear conventions, which usually yield the benefits of cleverness without the headaches.
Semantic cleverness becomes problematic too at times. There’s a fine line between developing a useful abstraction and doing something so obtuse your users are scarcely able to discern what’s going on once they run into a problem and run in circles trying to debug weird underlying language design decisions.
- Gibbon1 5y agoMakes me wonder if using keywords like var char foo; // foo is a char pointer char boo; // pointer to a boo type or something I want. alias baz = boo.foo; // bas is actually just an alias for boo.foo