I hope I’m not pushing my luck with this post.
Julia would be more perfect in my eye with camelCase names. I just run into
atreplinit(f) for the first time and it got me into deer caught in the headlights mode for a few seconds, before I was able to parse it as
atReplInit(f). What is the least readable name in standard Julia you know?
It’s got nothing on other languages. F77: xerbla, ilaver, …
Well, we had only 72 columns to use out of 80 on the punch card. One had to be very thrifty with the names…
A long time ago, there was
This goes straight to the top of the greatest hits list.
Edit: it’s so unreadable that I got it wrong, it’s
Along the lines of
splitext. Slightly OT.
But, the least memorable is the second of
#!@%$, I mean
Perhaps snake case would be more suited to Julia’s style
CamelCase all across the board.
Names of Types and Modules begin with a capital letter and word separation is shown with upper camel case instead of underscores.
Just extend this rule to names of variables beginning with a lower case letter. I’m not a big fan of snakes.
I find snakes very readable, and all my variables (other than the mathsy ones) are snake names. That said, I’d definitely take camelCase over the smashitalltogether style that Julia unfortunately ended up with.
I don’t mean to be contrarian, but I happen to be very happy with the status quo, even if it’s not perfect.
Snake name in isolation is the most readable one, I grant you that. Inside a dense code, it looks just too fragmented to my eye. Subjective, I know.
It’s good for fast typing and overall not too bad.
You make a good point. I had to read some R code recently that was full of loads of long snake names (with dots rather than underscores, as is common in R), and it was too busy to see what was going on easily. I renamed
current.time to simply
t, and my life became much easier!
cumsum always makes me snicker, childish I know…but there you have it.
It wouldn’t look more serious as