Re: [Boost-users] Library Interface Design

From: Sohail Somani (s.somani_at_[hidden])
Date: 2006-09-14 13:14:15

> -----Original Message-----
> From: boost-users-bounces_at_[hidden] 
> [mailto:boost-users-bounces_at_[hidden]] On Behalf Of 
> David Abrahams
> Sent: Thursday, September 14, 2006 4:07 AM
> To: boost-users_at_[hidden]
> Subject: Re: [Boost-users] Library Interface Design
> 
> Scott Meyers <usenet_at_[hidden]> writes:
> 
> > - It has to be easy to find and fix mistakes resulting from 
> incorrect 
> > usage of an API.  For example, APIs should throw exceptions clearly 
> > describing what needs to be done to fix the problems.
> 
> It's always better to detect the problems at compile-time, at least in
> the world of statically-checked languages.

I would echo that this statement is also true for dynamically-checked
languages in the obvious way. I think my python code is much easier to
read if there is only one way to get a good object.