(jeffa) Re: Private Classes - Same or Separate Files?

I personally like for each class to be in it's own file. That way, a user of your modules can (hopefully more) easily find what they are looking for when the time comes to dredge through the source code. This also makes documention easier to find as well. Document everything! Even if you are just saying "Don't instantiate this class!".

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

Comment on (jeffa) Re: Private Classes - Same or Separate Files?

Replies are listed 'Best First'.
Re: (jeffa) Re: Private Classes - Same or Separate Files? by herveus (Prior) on Mar 06, 2002 at 15:18 UTC
Howdy! I'm with jeffa here...at least in the general case. I do distinguish between "defining the class" and "diddling around in a class I've already gotten defined". In the latter, one might shift into the class to (re)define something or run some code in a different name space. yours, Michael	[reply]