<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">2013/12/24 Chris Muller <span dir="ltr"><<a href="mailto:asqueaker@gmail.com" target="_blank">asqueaker@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class="im">> The other point being whether to invoke new or basicNew is more germane, but<br>
> not invoking new is a way to tell my instances are not created like that.<br>
<br>
</div>It's a way to tell your instances not to initialize _default values_, if any.<br>
<br>
If a var is added and you add an initialize method, oops. You better<br>
change your constructor too, ha ha...<br>
<div class="im"><br></div></blockquote><div>Chris, that's not your best argument, what do you read here?<br></div><div>^self basicNew initializeWith: prefix<br> ^^^^^^^^^<br></div><div><br></div>
<div>Did you browse HashedCollection>>new: as I suggested?<br></div><div>It does not send #new, nor #initialize but #initialize:<br></div><div>This is fairly common in Squeak.<br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class="im">
> We<br>
> could push it further and redefine new ^self error as you suggested, but<br>
> it's quite heavy...<br>
<br>
</div>Default values.<br>
<br>
</blockquote></div>Nah! We ain't gonna need such mock-ups, or we'll explicitely create some.<br></div></div>