[squeak-dev] Should class comments be separated from source code?

liang bing liangbing64 at gmail.com
Sun Mar 23 06:44:59 UTC 2014


Should class comments be separated from source code?

I think it should be separated into two files, the reasons are,

1.	current comment not enough for understood (less or nothing)
2.	if I added new comment , it is not convenient when update or load new
packages
3.	comment is knowledge about how to use, how to change the application, it
could be shared and accumulated
4.	comment should be stand alone as  knowledge base with different local
languages


I hope Squeak 4.6 gives a new comment tool in system browser
Three files: Soure file, Changes and Comments file,

Hope Squeak better!

Liang Bing




--
View this message in context: http://forum.world.st/Should-class-comments-be-separated-from-source-code-tp4750381.html
Sent from the Squeak - Dev mailing list archive at Nabble.com.


More information about the Squeak-dev mailing list