By jdegoes
via jdegoes.squarespace.com
Published: May 11 2009 / 23:55
In Part 3 of Good API Design, John A. De Goes discusses how you can use the type system to make your APIs harder to misuse. Why require clients to read and memorize documentation when you can make the compiler enforce your rules? Several examples are presented, including a new face on Java's poorly designed socket API. Join the discussion of good API design by contributing your answers to the provided exercises!
Add your comment
Voters For This Link (14)
-
jdegoes -
boyarsky -
GreatWallWarrior
-
rsmaniak
-
Egnaro
-
tenshi
-
mosessaur -
vatsanvindictive -
kismilan
-
skaboss
-
hl12278
-
greenday -
larsgregersen
-
vicento.ramos
