Sponsored Link •
A Weblog by Bruce Eckel
B. Scott Andersen
Vladimir Ritz Bossicard
James O. Coplien
Cees de Groot
David Heinemeier Hansson
Jakob Eg Larsen
Robert C. Martin
John D. Mitchell
Eric S. Raymond
Guido van van Rossum
Richard Hale Shaw
August 31, 2005, 7 comments
A reader questioned my project-estimation technique in "Thinking in C++, Volume 1."
August 30, 2005, 7 comments
I've just finished reading "Java Puzzlers: Traps, Pitfalls, and Corner Cases" by Joshua Bloch and Neal Gafter (Addison Wesley, 2005).
August 26, 2005, Submit comment
The slides and audio from my presentation at the 2005 Python conference are now available.
August 21, 2005, 12 comments
Ian Bicking creates the first reasonable analysis (that I know of) between the two languages.
August 20, 2005, 53 comments
While experimenting to find a good introductory exercise for the PriorityQueue class, I discovered several anomalous results which I think produce a higher-order exercise in library design.
August 8, 2005, 2 comments
Mike Levin has posted another audio interview with me, which we recorded yesterday using Skype. It's about an hour long.
August 5, 2005, 11 comments
I've been working on this since the first post of this example; you can see that the code has been completely rewritten and (I think) greatly improved, both in terms of the generics and the performance tests themselves.
August 4, 2005, 35 comments
A few years ago, close on the heels of the dot-com bust, Rational basically imploded. IBM felt that there was still value in what was left of the company, and paid an exorbitant amount for the remains.
July 26, 2005, 6 comments
This entry is a replacement for "When Generics Fail" (which was deleted). In that, I began with casting solution, thinking that there wasn't a generic solution, then Krzysztof Sobolewski corrected me. So instead, I will compare the two solutions.
July 22, 2005, 12 comments
A comment to an article by Craig Larman posted last year.
July 19, 2005, 2 comments
From discussions about the previous weblog entry, I've realized that Collection, Iterator (and Iterable) are all attempts to unify access to containers. Each has strengths and weaknesses, which is probably why we need more than one way to do it.
July 14, 2005, 18 comments
According to the Design Patterns book (aka GoF), the intent of the Iterator pattern is to "Provide a way to access the elements of an aggregate object sequentially without exposing its underlying representation." Or more simply, an iterator unifies access to containers.
July 12, 2005, 24 comments
For Thinking in Java 4e, I'm trying to analyze the presence of the Collections interface in java.util.