|
Scott Klement wrote: > > I think you wanted to use cvthc, rather than cvtch > . > I posted samples of calling these functions here: > http://archive.midrange.com/rpg400-l/200205/msg00309.html > > The problem, I believe is that it's trying to read 8 bytes starting > at the beginning of your 'alp4HexBytes' variable. Since that extends > 4 bytes past the end of the parameter, it gives you the error that > you can't access the memory at that offset. > I prefer to use other names than cvthc and cvtch for the prototypes for these functions. I just cannot make it stick in my brain which is h and which is c. Unlike Bob, I don't think either meaning makes sense - x'f0' and 'f0' both seem to fit h and c equally well. Here are the prototypes I would use: http://faq.midrange.com/data/cache/114.html The offset error isn't quite as simple as going past the end of the parameter. There's almost always accessible storage there. It's that the following 4 bytes of storage doesn't have valid 2-byte hex values. I don't know why this causes an offset error, but I assume it's something internal to the function that's getting invalidly offsetted.
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.