Today was a rain day, so no digging. Dad and I covered the dig site and the tractor last night.
A little background: My parents are building an addition on the house. After much deliberation, they decided that they could do all of the work (architecture, management, construction) by themselves; this saves a significant amount of money and gives them total control over the project. The whole family is in on the project. My older brother and I are being paid for construction work, which is better pay than I would get from a short-notice summer or campus job, and it's a lot of fun.
My current task is to excavate a significant chunk of the backyard so that we can lay down the foundation, using a gasoline-powered frontloader/backhoe tractor named Gimli. Yes, Gimli. The low wooden boundary for the dig site is called the Deeping Wall. Our pneumatic nail gun is named Glamdring. My dad has a thing for Lord of the Rings names, and it may seem a bit corny at first gloss, but I think it's cool. And it's more fun to say "Hand me Glamdring" than "Hand me that large pneumatic nailer over there".
I saw Spiderman The Second today. I liked it. A lot. Look ma, no spoilers!
Aside: Oz's delegation and named method syntax seems dumb to me. It seems like you'd want "meth A" to mean "set A as method name at class definition" and "meth !A" to mean "look at me! I'm creating a local name A!", not the other way around. And what's this "meth otherwise(M)" crap for delegation? Wouldn't "meth M" be cleaner? Only a zero-arity record could possibly be confusing under this syntax, and then you'd have to write "meth A()" regardless. Besides that, though, and the general sense of unease that dynamic typing gives me, I like this object system. However, unless Oz has suddenly acquired a significant following among my LJ readers, only
qedragon is going to understand any of this.
A little background: My parents are building an addition on the house. After much deliberation, they decided that they could do all of the work (architecture, management, construction) by themselves; this saves a significant amount of money and gives them total control over the project. The whole family is in on the project. My older brother and I are being paid for construction work, which is better pay than I would get from a short-notice summer or campus job, and it's a lot of fun.
My current task is to excavate a significant chunk of the backyard so that we can lay down the foundation, using a gasoline-powered frontloader/backhoe tractor named Gimli. Yes, Gimli. The low wooden boundary for the dig site is called the Deeping Wall. Our pneumatic nail gun is named Glamdring. My dad has a thing for Lord of the Rings names, and it may seem a bit corny at first gloss, but I think it's cool. And it's more fun to say "Hand me Glamdring" than "Hand me that large pneumatic nailer over there".
I saw Spiderman The Second today. I liked it. A lot. Look ma, no spoilers!
Aside: Oz's delegation and named method syntax seems dumb to me. It seems like you'd want "meth A" to mean "set A as method name at class definition" and "meth !A" to mean "look at me! I'm creating a local name A!", not the other way around. And what's this "meth otherwise(M)" crap for delegation? Wouldn't "meth M" be cleaner? Only a zero-arity record could possibly be confusing under this syntax, and then you'd have to write "meth A()" regardless. Besides that, though, and the general sense of unease that dynamic typing gives me, I like this object system. However, unless Oz has suddenly acquired a significant following among my LJ readers, only