The Raku Programming Language Collect, Conserve and Remaster Project
Originally published on 29 April 2010 by Carl Mäsak.
This is three thirds of a post. The three parts will simply have to combine into one big mechbot in order to pass as a whole post.
I sent in a proposal, and it got accepted. Yay!
Sometimes you both want do subdivide methods into small manageable parts, all the while keeping some sort of data between them. Most people reach for the instance attributes to do this, since these shared between all the methods of one object.
But this can also be done with contextuals, as is now done in Yapsi. This keeps the lifetime of the variables as short as possible, and keeps the objects light-weight. And it still works with inheritance.
I like how Raku allows me to mix OO and contextuals this way. And I really like that it works in Rakudo already.
I’ve blogged before about how #raku is a small, friendly community which turns even flame wars into interesting discussions and which works on being kind and open. We’ve had a bit of troll activity since I wrote those posts, as well as a few borderline trolls.
The other day I treated someone with undue impatience. The whole episode ended well, and I’ve apologised. In short, what looked like nagging questioning may simply have been someone’s slightly different means of communicating.
Mean and evil acts are often committed by people convinced that they’re actually doing good. mst++ writes about the reasons for being harsh, and I thought this was one of those times when that was called for. It wasn’t.
It taught me to look out for situations when I might be mistaking variations in personality and communication skills for truly annoying behaviour. In many ways, that’s a refreshing reminder: a really open community requires that we recognize that everyone doesn’t operate exactly the same as we do. That sounds terribly clichéd, I know; but forgetting it is also far too easy.