Am I missing something? If I have a procedure called VectorAdd and at some later date I decide I want to overload it to a new 'VectorAdd' with different parameters, I now have to rename the orignial procedure to something else because otherwise I get a duplicate name. Renaming it will obviously force me to recompile everything that is currently using my Service Program so I really want to avoid that, but I can't see how to get around this. What have other people done in similar situations? Is there a cunning work-around?
Just to be clear. if I have this:
VectorAdd(@Vector:@NewElement) ;
and I decide I want to have a new procedure which accepts another parameter, like this:
VectorAdd(@Vector:Index:@NewElement) ;
I can't use overloading to do that without renaming the original VectorAdd procedure, correct?
Just to be clear. if I have this:
VectorAdd(@Vector:@NewElement) ;
and I decide I want to have a new procedure which accepts another parameter, like this:
VectorAdd(@Vector:Index:@NewElement) ;
I can't use overloading to do that without renaming the original VectorAdd procedure, correct?
Comment