|
>> If CL character variables are aligned on a 16-byte boundary, then if you just receive the value from one procedure and pass it to another without manipulating it, you should be okay. In any language apart from CL I'd agree with you, but I've seen CL generate some really strange code over the years including moving input parms to a temp area and then back again (which would invalidate a "faked" pointer). Personally I don't think it is worth the risk - even if it works today ..... Jon Paris Partner400
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.