I'm still a little flabbergasted by how nicely these sections on subprograms and functions programmers coincided with my most recent question on the Q&A. The powers that be do not want me confused, even for a second.
Most of this business was pretty straightforward, I thought. My eyes did glaze over a bit during 9.5.6 (Multidimensional Arrays as Parameters), but I'm not actually sure if that's important enough for us to go over in class.
It would be great, though, if we could talk about the pass-by-name method! Not sure I've caught that yet, even after seeing it a bit in Scala. And I sense it's going to be relevant when we look at the functional paradigm, when that happens.
Python has a cool thing going on with its def statements being executable. With certain functions (if they're brief enough that this wouldn't impair readability), seems like it could be nice to have their bodies be conditional (as in the way the book demonstrates at the top of p. 390).
Keyword parameters seems like a pretty epic thing to me, so I don't know what you're on about with that, Brooks. Sure helps readability when you've got all kinds of parameters flying around. I do agree with you on the matter of Ruby's parameter system being complex, though. It's just flat out scary, really... Fortunately, I've been able to find absolute boatloads of hipsters talking about this stuff (and hopefully making it clearer) here, here, here, and here.
Personally, I would have liked it if the book had referred to its actual parameters and formal parameters as arguments and parameters, respectively. Or would that have been less precise? Are they completely interchangeable?
No comments:
Post a Comment