<!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: My first morph</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Bert wrote:</FONT>
</P>
<P><FONT SIZE=2>> Missing class comments are indeed a problem. However, code </FONT>
<BR><FONT SIZE=2>> documentation generally is deemed less necessary, since Smalltalk </FONT>
<BR><FONT SIZE=2>> itself is rather verbose compared to other programming languages. In </FONT>
<BR><FONT SIZE=2>> addition, unit tests are seen as a good way to both document and </FONT>
<BR><FONT SIZE=2>> verify behavior. Like, in EventTest, you see many examples of how you </FONT>
<BR><FONT SIZE=2>> can use events.</FONT>
</P>
<P><FONT SIZE=2>Ok, rant over, it was trivial and does exactly what I want. Is there some way to know there is a test class or does one rely on a naming convention like System-Object Events-Tests in this case.</FONT></P>
<P><FONT SIZE=2>> But the most important thing for a Smalltalk novice is to learn how </FONT>
<BR><FONT SIZE=2>> to use the coding tools to explore the system. Senders, implementors, </FONT>
<BR><FONT SIZE=2>> inst var refs, class refs etc. are just a key-stroke away and help </FONT>
<BR><FONT SIZE=2>> you to get to know everything.</FONT>
</P>
<P><FONT SIZE=2>I am getting there.</FONT>
</P>
<P><FONT SIZE=2>> Btw, it would be nice if you stop sending HTML mails to the list - we </FONT>
<BR><FONT SIZE=2>> prefer plain text.</FONT>
</P>
<P><FONT SIZE=2>I will try and remember</FONT>
</P>
<P><FONT SIZE=2>Thank you for the help Bert.</FONT>
</P>
<P><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>