>> No, but please remember that in the future we add strong typing. >> If you will want to enable type protection in your code then you >> will have to precisely declare parameters with type in your class >> definition so it's possible that you will make reverted modification. > > i understand but declaring parameters both in class definition and in > method implementation is a duplication of code and as we've seen a > source of ( formal ) errors. > > In class(y) doc methods are always declared without any parameter. > > It would be better to have only one method declaration/implementation > inside the class definition but if it's not possible declaring methods > without parameters seems to be the "second best" solution.
Just a Harbour SVN related comment: As for code going into Harbour SVN, I'd like to ask everyone to always add full parameter list to declaration too. This usually gives a good overview of the class functionality and usage, and in many places INLINE METHODs are used, which would need parameters in declaration anyway, so to avoid a "hybrid" look, the parameter list is best to be put for every declaration. It's also a nice way to visibly differentiate methods from variable declarations in class header code. [ And true, eventually class declaration may go into a headers, or be needed for strong typing. ] Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
