io,
While I am greatly enjoying your terse and good solutions (Even attempting to emulate your approach to answering questions to some extent), I find I do have a request. If possible, please use slightly more verbosity in your variables. It improves the readability of the code for us less fluent, and allows less expirienced monks like myself to focus on your construction more closely.
coreolyn -- Working to have perl code flying off his fingers instead of spelling mistakes.
| [reply] |
In this case the variable names are clearly my fault. My names tend to be more verbose when I am not being silly.
Sorry.
| [reply] |
Thank you for the feedback, I'll try to keep that your suggestion in mind.
In this case I was trying to emphasize the similarity
to tilly's code.
But I'm interested to know what variable names you would have chosen
for improved readability?
| [reply] |
I confess I was reading your post out of context and didn't slow down to see that it was tilly's context that you were improving -- my bad. (I definately abuse impatience). However, I think it's single letter vars that distract me the most (except $i). If tilly s/\$bucket/\$n/g then both examples would have been more legible.
coreolyn - Slowly learning to shut-up till he has all the facts digested.
| [reply] |