Hi, I was reading the coding conventions which says, "every root class that implements #initialize must have a #new on the class side" and I was wondering, if the following is implied on subclasses of WAComponent and WATask:
<div><div><br class="webkit-block-placeholder"></div><div>class methods:</div><div><br class="webkit-block-placeholder"></div><div>WRONG</div><div><br class="webkit-block-placeholder"></div><div>new</div><div>&nbsp;&nbsp; &nbsp;^super new initialize
</div><div><br class="webkit-block-placeholder"></div><div>CORRECT</div><div><br class="webkit-block-placeholder"></div><div>new</div><div>&nbsp;&nbsp; ^self basicNew initialize</div><div><br class="webkit-block-placeholder"></div>
<div><br class="webkit-block-placeholder"></div><div>If the above is correct, is this the case for classes that are subclassed from &nbsp;Object?</div><div><br class="webkit-block-placeholder"></div><div>Thanks in advance,</div>
<div><br class="webkit-block-placeholder"></div><div>-Conrad<br><br><div><span class="gmail_quote">On 8/31/07, <b class="gmail_sendername">Philippe Marschall</b> &lt;<a href="mailto:philippe.marschall@gmail.com">philippe.marschall@gmail.com
</a>&gt; wrote:</span><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">2007/8/31, Michael Lucas-Smith &lt;<a href="mailto:mlucas-smith@cincom.com">mlucas-smith@cincom.com
</a>&gt;:<br>&gt; Philippe Marschall wrote:<br>&gt; &gt; 2007/8/30, Michael Lucas-Smith &lt;<a href="mailto:mlucas-smith@cincom.com">mlucas-smith@cincom.com</a>&gt;:<br>&gt; &gt;<br>&gt; &gt;&gt; Hello Seasiders,<br>&gt; &gt;&gt;
<br>&gt; &gt;&gt; Squeak has the #initialize pattern on Object - but VisualWorks doesn&#39;t.<br>&gt; &gt;&gt; I&#39;m not sure about Gemstone or Dolphin.<br>&gt; &gt;&gt;<br>&gt; &gt;&gt; Aside from the argument that may be we should have that pattern too- in
<br>&gt; &gt;&gt; the interest of code portability, what is the best approach here.<br>&gt; &gt;&gt;<br>&gt; &gt;<br>&gt; &gt; Acutally this issue like many others is covered in the Seaside coding<br>&gt; &gt; conventions:
<br>&gt; &gt; <a href="http://www.seaside.st/communit">http://www.seaside.st/communit</a>y/conventions<br>&gt; &gt;<br>&gt; &gt; I just simply forgot is in this case. Seaside2.8a1-pmm.463 should fix this.<br>&gt; &gt;<br>
&gt; Thanks. I was a little surprised, as I hadn&#39;t seen this previously. I<br>&gt; figured if it were a common problem, it would have been happening<br>&gt; everywhere. Good to see it&#39;s covered in the conventions :)
<br><br>That&#39;s mostly thanks to Michel Bany. For a long time he helped<br>increase the portability by making us aware of our &quot;sins&quot; and fixing<br>unportable stuff.<br><br>Cheers<br>Philippe<br><br>&gt; Michael
<br>&gt; _______________________________________________<br>&gt; Seaside mailing list<br>&gt; <a href="mailto:Seaside@lists.squeakfoundation">Seaside@lists.squeakfoundation</a>.org<br>&gt; <a href="http://lists.squeakfoundation">
http://lists.squeakfoundation</a>.org/cgi-bin/mailman/listinfo/seaside<br>&gt;<br>_______________________________________________<br>Seaside mailing list<br><a href="mailto:Seaside@lists.squeakfoundation">Seaside@lists.squeakfoundation
</a>.org<br><a href="http://lists.squeakfoundation">http://lists.squeakfoundation</a>.org/cgi-bin/mailman/listinfo/seaside<br></blockquote></div><br></div></div>