I looked at the list of requirements and you need to ask why the items are there. If the mission statement is flawed you will have problems. I haven't heard of this approach for many years, this was the way it used to be done, a bit more
cerebral, I think. But why do you think you need
overloading. I assume you want to maiantain the code for some time. Visual PL/I from IBM is probably what you want, you don't want to train future maintainers about your overloaded class libraries
Slashdot Mirror
I looked at the list of requirements and you need to ask why the items are there. If the mission statement is flawed you will have problems. I haven't heard of this approach for many years, this was the way it used to be done, a bit more cerebral, I think. But why do you think you need overloading. I assume you want to maiantain the code for some time. Visual PL/I from IBM is probably what you want, you don't want to train future maintainers about your overloaded class libraries