Much like Keith Bennett I’m not used to parentheses playing such an important role in the way that an expression gets evaluated.

As I understand it if an expression is enclosed in parentheses then that means it will be evaluated as a function.

For example I spent quite a while trying to work out why the following code kept throwing a class cast exception:

If you run that code in the REPL you’ll get the following exception because 'true' isn’t a function and therefore can’t be applied as such:

If we don’t want something to be treated this way then the parentheses need to disappear!

Somewhat related to the above is understanding which expressions evaluate to 'true' or 'false'.

I’m told there are some edge cases but that as a general rule everything except for 'false' and 'nil' evaluates to true.

I think that’s an idea which is more common in languages like Ruby but I’m not yet used to the idea that we can something like this and have it execute:

In C# or Java I would except to have to compare "mark" to something in order for it to evaluate to a boolean result.

It seems like a really neat way to reduce the amount of code we have to write though so I like it so far.

I’ve been working through Mark Volkmann’s Clojure tutorial and in one example he defines the following function:

I wanted to try it out to see if a certain character was a vowel so I initially did this:

"a" is actually a string though which means it’s an array of characters when what we really want is a single character.

I thought the following would be what I wanted:

Instead what I got was the following exception:

This one just turned out to be a case of me not reading the manual very carefully and actually the following is what I wanted: