|
Why not encapsulate all operation codes? For instance instead of allowing x=y+z; Have them do this instead x=OurAdd(y : z : %size(x) : %decpos(x) : ErrDS); The possibilities are that you can handle overflow's, etc within your procedure. Then again, you can decide, like I do, that encapsulating all this stuff is only exciting to those who write the encapsulation routines. Rob Berendt
This mailing list archive is Copyright 1997-2026 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.
midrange.com
