> One for the design itself and one for describing the usage at design or runtime.
Why put the burden on code? Something like this is the programmer's responsibility, no need to add more bloat to the final code. What the program doesn't use or the user doesn't see should never be in the executable. > Smalltalk has it Show me one example, what I know is that there's only one way to comment in Smalltalk and that makes use of class property. -- View this message in context: http://free-pascal-general.1045716.n5.nabble.com/Should-TObject-or-TComponent-have-a-Comment-property-tp5715746p5715747.html Sent from the Free Pascal - General mailing list archive at Nabble.com. _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
