Lists Home |
Date Index |
From: "Rich Salz" <firstname.lastname@example.org>
> Yes, you can write an optimized codepath that does this, falling back
> (or falling over :) when it finds other entities, but it should be clear
> that if you *never* have those things, then your code can be smaller
> (and therefore more reliable), and faster.
It is not clear to me that it would be any faster, since it involves branches
that would never be taken if the data contained no user-defined entities.
As for code being more reliable, the metrics people AFAIK seem to
say that the benefits of small size (i.e. the removal of the risk of errors
due to code complexity) can be gained on projects of any size
by factoring your code into simple enough units (or focussing your
testing on risky sections). It is not the absolute size but the code
complexity that makes small systems unreliable.