<div>Igor, could you please give a link to the article where Gilad speaks about it?</div>
<div>(I can not find anything related in his blog)</div>
<div> </div>
<div>Danil<br><br></div>
<div class="gmail_quote">2008/5/7 Igor Stasenko <<a href="mailto:siguctua@gmail.com">siguctua@gmail.com</a>>:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I read Gilad's blog and having some concepts which i think is<br>redundant and smell like javaisms.<br>
For instance, i don't share the view, that all fields in class<br>instance should be initialized and initialized once, by constructor<br>(instance factory method).<br>What about lazy initialization?<br>What if superclass initializes ivar with something, then using that<br>
ivar during rest of initialization phase, and then at subclass<br>initialization it can be overridden by another value, after done<br>initializing superclass.<br>I think that language shouldn't care or enforce rules aka<br>
'constructors', its totally redundant to me. Developer should know<br>himself, how and where initialize ivars, not in compiler/constructor.<br><br>Declaring private/public fields looking redundant too: they should be<br>
always private.<br>Instead, accessors #foo, #foo: can be made public or private by the will.<br>But if you make field public, then it's accessors became public as<br>well? But what if i want #foo to be public, but #foo: to be private?<br>
<div>
<div></div>
<div class="Wj3C7c"><br>--<br>Best regards,<br>Igor Stasenko AKA sig.<br><br></div></div></blockquote></div><br>