News for hackers. Stuff that matters.
Re:An Interview with Brian Kernighan: Breeding Little Languages by ggchappell on Saturday April 11, 2009 @04:11PM (#557785)
> Should examples--even beginner examples--include the error-handling code?

> Brian: I'm torn on this. Error-handling code tends to be bulky and very uninteresting and uninstructive, so it often gets in the way of learning and understanding the basic language constructs. At the same time, it's important to remind programmers that errors do happen and that their code has to be able to cope with errors.

The lesson we learn from this is that we should design languages so that error-handling code does not have to be "bulky".

Re:An Interview with Brian Kernighan: Breeding Little Languages by snprbob86 on Sunday April 12, 2009 @02:25AM (#558229)
Or, leave error-handling code just as bulky as it is, but design languages in which errors need to be handled less frequently.
Re:An Interview with Brian Kernighan: Breeding Little Languages by ced on Saturday April 11, 2009 @10:53PM (#558095)
Do you know any language where it's not bulky?
Re:An Interview with Brian Kernighan: Breeding Little Languages by ggchappell on Sunday April 12, 2009 @02:28PM (#558724)
> Do you know any language where it's not bulky?

Good question. Off the top of my head, I'd say, "no".

OTOH, one can look at relative bulkiness. E.g., I've found that dealing with exceptions in Python is significantly less work than in C++.