On 10/2/06, Jonathan Lang <[EMAIL PROTECTED]> wrote:
I'm not used to programming styles where a programmer intentionally and explicitly forbids the use of otherwise perfectly legal code. Is there really a market for this sort of thing?
This reminds me of the endless student "proofs" that trisect the angle using euclidean geometry; i.e. the fact that people won't accept that you can prove something is impossible. The same philosophy applies here: if you don't allow code that forbids other code from doing something, then you are forbidding code from doing something, violating your own principle. However, all this philosophical gobbledygook doesn't mean much in the real world. Another interesting note is that you could consider a policy-based object model to be forbidding certain code. But I prefer to think of it as a more accurate definition: "you are not a hatter unless the hats you make are hats". Luke
