<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>Re: Squeaking trouble</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>All</FONT>
</P>
<P><FONT SIZE=2>> x := SequenceableCollection new, then try to print x. Lock-up + 100%</FONT>
<BR><FONT SIZE=2>> CPU. The only response is from the main window, quit without saving then </FONT>
<BR><FONT SIZE=2>> kill squeak as it's still running.</FONT>
</P>
<P><FONT SIZE=2>Thank you to everyone for the discussion and the tips. I enjoyed reading it. I now save my image much more frequently. Things like this become much less of an issue once they are understood. In my defense I would say that I didn't read the comments for the class, my fault. However, apart from the comment I am at a loss to understand what makes this class abstract, there is no special protocol in the class definition and all the methods appear to have an implementation. I was expecting to find subclassResponsibility somewhere like it says in <A HREF="http://minnow.cc.gatech.edu/squeak/472" TARGET="_blank">http://minnow.cc.gatech.edu/squeak/472</A>. </FONT></P>
<P><FONT SIZE=2>> I was simply trying to understand why forceTo: paddingStartWith: </FONT>
<BR><FONT SIZE=2>> didn't work if the length was more than the original string.</FONT>
</P>
<P><FONT SIZE=2>On this point which I think got masked by the first point. I have now discovered that '0' is not the same as $0. Saying paddingStartWith: '0' gives an indexing error. Probably blindingly obvious to anyone who has worked with Smalltalk for a while. </FONT></P>
<P><FONT SIZE=2>Regards</FONT>
<BR><FONT SIZE=2>Bob</FONT>
</P>
<P><STRONG>*** Confidentiality Notice ***</STRONG>
Proprietary/Confidential<BR>Information belonging to CGI Group Inc. and its
affiliates<BR>may be contained in this message. If you are not a
recipient<BR>indicated or intended in this message (or responsible
for<BR>delivery of this message to such person), or you think for<BR>any reason
that this message may have been addressed to you<BR>in error, you may not use or
copy or deliver this message<BR>to anyone else. In such case, you should
destroy this<BR>message and are asked to notify the sender by reply
email.</P>
</BODY>
</HTML>