|
>>With a service program I can change the parameter list to an existing >function, or let a completely different >>function (with a changed parameter list) take over the name of an old >function; and still let old programs >>using the old function work without modification or recompilation. How would >you accomplish this with your >>CallM opcode? >What you are describing is similar to function overloading. same function >name, different argument types or number >of arguments. Two completely separate modules. One of the great contributions >of c++ and bjarne stroustrup. ( if he >did not invent it, he sure showed how well it could work, esp when combined >with templates. ). In the first case I wasn't thinking of changing arguments types, just adding new parms. >In my opinion, what you are describing is a bad programming method. Adds more >complexity to the system. If the new >module does something different that the old module, give it a new name or use >a typed language that supports overloading. The new module need not do something different (if it does, I agree it should have a new name), but I have done this once were the underlying database changed, and I wanted to keep the name since it was performing the same "logic", although with a completely rewritten interface. >Or if you can justify this practice and agree that cpu is virtually free, >introduce an OvrPgm or OvrMod command. >When the module is called from the old pgms, override the call to the old >module. I don't know, but I believe that service programs with different versions "inside" don't impose a large cpu overhead. Should only require an added entry point table plus the extra executable code. +--- | This is the MI Programmers Mailing List! | To submit a new message, send your mail to MI400@midrange.com. | To subscribe to this list send email to MI400-SUB@midrange.com. | To unsubscribe from this list send email to MI400-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: dr2@cssas400.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.