|
Thanks, Paul. That's exactly what I was referring to. And while this is an absolutely wonderful capability, the compiler gives you no notice you that the conversion is occurring, which could lead to inadvertent performance problems. For example, you probably don't want to call an API over and over with a 65535A CONST parameter. I wonder if we ask Barbara nicely if she would give us some optional severity 00 messages when this occurs? Perhaps a compiler option like *IMPCNVWRN for "implicit conversion warning", which would generate some nice mellow severity zero RNF errors when such a conversion takes place. Joe > From: Paul Morgan > > Kurt, > > If the parameter passed doesn't match the required parameter (size, > decimals > and numeric type) the compiler can safely convert the parameter to the > right > format. This copying/conversion of the parameter before the call is a > performance hit.
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.