Dan Weinreb wrote:<div>&quot;<span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">At least one reason, and maybe the only reason,</span></div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">is that the initial value is figured out in a way<br>
that may depend on class precedence.&quot;</span><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><br></span></div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">Well, another reason is that they&#39;re associated with the class, and can thus be introspected as part of some protocol where you supply a class as an argument.</span></div>
<div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><br></span></div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">I&#39;m not recommending that or anything. You would be better off designing some sort of specification object which included both a class AND those values. I&#39;m just pedantically addressing your &quot;only reason&quot; speculation. :=)</span></div>
<div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><br></span></div>