Help coderanch get a
new server
by contributing to the fundraiser
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Scala puzzlers question

 
Ranch Hand
Posts: 69
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Dear Authors,
Welcome and thanks for your time here!

Puzzles are a great and fun way to learn about the intricacies of a language. "C traps and pitfalls" by Andrew Koenig, "The C puzzle book" by Feuer and "Expert C programming" by Linden are superb. So is the "Java Puzzlers" book. I remember all these books showing just a handful of code snippet to drive a point home.
What is the average length of the puzzles? Does it cover any design "gotchas"?

--- regards atul
 
Author
Posts: 17
5
Scala
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Atul

> What is the average length of the puzzles? Does it cover any design "gotchas"?

Thanks for your question! The chapters in the book - one puzzler per chapter - (see Nermin's comment for some more detail of the difference between the book and the Scala Puzzlers site) are 4-6 pages in length, on average. The code samples themselves are as short as possible - the principle being that if a one-line statement that seems obvious behaves in an unexpected way, that's even more puzzling than if a loooong block of code works slightly differently from what you might expect. The result is that the puzzler examples tend to be too short to get into the realm of "system design".

Some of the lessons the follow from a couple of the puzzlers could be classed as "design guidelines", but in the main the aim of Puzzlers is to teach you about a language feature, quirk or interaction that you were not aware of or - more valuable still - thought you had understood, but didn't understand completely.

Regards

ap
 
If a regular clown is funny, then a larger clown would be funnier. Math. Verified by this tiny ad:
We need your help - Coderanch server fundraiser
https://coderanch.com/t/782867/Coderanch-server-fundraiser
reply
    Bookmark Topic Watch Topic
  • New Topic