crafty-chameleon: asserts

[Adrian Mowat]

Brian,

On page 54, you asked...

Readers: should I have introduced assertions earlier? Have you run into these problems before this chapter?

Personally, I didn't find any problems confusing maps and symbols while working through the exercises.  I have a fair amount of Clojure experience and I code Ruby for a job so maybe people new to clojure and/or languages influenced by lisp might have found this more difficult.

As an aside, the hardest one to get into my head was the move to defining :__class_symbol__ on construction using :__own_symbol__.  

Hope this helps

Adrian

[JuanManuel Gimeno Illa]

I've never used assert directly. What I've done instead is use :pre and :post conditions in some functions. 

And nil haven't been a problem. I treat it as no-result and try to program my functions to nicely propagate it using lots of when expressions) and keep instead of map.

Juan Manuel

[Brian Marick]

On Jul 14, 2012, at 2:36 PM, Adrian Mowat wrote:

> As an aside, the hardest one to get into my head was the move to defining :__class_symbol__ on construction using :__own_symbol__.

Yeah, there's something wrong with the name :__own_symbol__ -- somehow its meaning doesn't stick in my head.

-----
Brian Marick, Artisanal Labrador
Contract programming in Ruby and Clojure
Occasional consulting on Agile

[Adrian Mowat]

It's not quite right, but something like :__template_class_symbol__  or :class_definition_symbol might be a bit stickier

On 20 Jul 2012, at 22:32, Brian Marick wrote:

As an aside, the hardest one to get into my head was the move to defining :__class_symbol__ on construction using :__own_symbol__.  

Yeah, there's something wrong with the name :__own_symbol__ -- somehow its meaning doesn't stick in my head.

Adrian Mowat

Tweet: @mowat27

Am I being a bit short?  Here's why: http://emailcharter.org/, http://inboxzero.com/