Bert wrote:
Missing class comments are indeed a problem. However, code documentation generally is deemed less necessary, since Smalltalk itself is rather verbose compared to other programming languages. In addition, unit tests are seen as a good way to both document and verify behavior. Like, in EventTest, you see many examples of how you can use events.
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.
But the most important thing for a Smalltalk novice is to learn how to use the coding tools to explore the system. Senders, implementors, inst var refs, class refs etc. are just a key-stroke away and help you to get to know everything.
I am getting there.
Btw, it would be nice if you stop sending HTML mails to the list - we prefer plain text.
I will try and remember
Thank you for the help Bert.
- Bob -
*** Confidentiality Notice *** Proprietary/Confidential Information belonging to CGI Group Inc. and its affiliates may be contained in this message. If you are not a recipient indicated or intended in this message (or responsible for delivery of this message to such person), or you think for any reason that this message may have been addressed to you in error, you may not use or copy or deliver this message to anyone else. In such case, you should destroy this message and are asked to notify the sender by reply email.
Am 09.11.2005 um 13:57 schrieb Bob.Cowdery@CGI-Europe.com:
Bert wrote:
Missing class comments are indeed a problem. However, code documentation generally is deemed less necessary, since Smalltalk itself is rather verbose compared to other programming languages. In addition, unit tests are seen as a good way to both document and verify behavior. Like, in EventTest, you see many examples of how
you
can use events.
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.
This, and "senders of" :-) It will also show uses in test classes.
Btw, it would be nice if you stop sending HTML mails to the list
- we
prefer plain text.
I will try and remember
But your message was HTML again ;-)
- Bert -
Most HTML mail should come with a plain text alternative part; if the the list policy is no HTML, I hope it's configured to use the plain text alternative automically.
Am 09.11.2005 um 21:52 schrieb Simon Michael:
Most HTML mail should come with a plain text alternative part;
That's not the point, of course nowadays virtually everyone, including me, can read the HTML mails. However, forcing your choice of fonts and sizes onto me (which HTML allows you to do, unfortunately) is not nice. I don't like having to manually increase the point size to make out what you wrote.
if the the list policy is no HTML, I hope it's configured to use the plain text alternative automically.
It's useful in certain rare cases to be able to sent and have people receive an HTML email. Thus we do not strip HTML generally. However, it's considered polite to send plain text mails. This is a developer's mailing list, every subscriber should be able to configure the mail client to send plain text.
- Bert -
squeak-dev@lists.squeakfoundation.org