There are lots of bad reasons to count lines of code, but lots of good reasons too. If you're porting some old code from one language to another, the more LOC in the old code, the longer it will probably take. If you're hunting for a bug, the more code you have to look through to find it, the harder it might be. Etc. It wasn't asked super eloquently but I think it's a highly constructive question.

Haskell has a way to express ranges, pretty similar to the Bash syntax from choroba's answer.

I think the idea is that less boilerplate means it's easier to get right.

Guava is code.google.com/p/guava-libraries

It's not constructive to ask why a language is designed the way it is, particularly if that design asks us to type four extra characters for no obvious benefit? What am I missing?

Just for the record, Haskell is 10 years older than C# :)

It seems to me that it might be helpful to think about what you want to do with these note/chord/scale classes. Are you going to produce sheet music? Midi files? Do transformations on scores (transposition, doubling all the note lengths, adding trills to all whole notes above a certain note, etc.)? Once you have a possible class structure, think about how you would accomplish those tasks. If it seems awkward, maybe you want a different class structure.

If you highlight your code and click the {} button, then the site will format it to look like code.