|
... and let me guess. You want full descriptor, and still be writing V3R2 code? dhandy@isgroup.net on 03/08/2000 12:49:08 PM Please respond to RPG400-L@midrange.com@Internet To: RPG400-L@midrange.com@Internet cc: Fax to: Subject: Re: Bale, Dan Hans, >but a few months or a few >years later, someone (maybe even you) will write some code >passing a value outside the supported range. Point taken. As I said, I have never had to even come close to that size in a business app yet (aside from EVAL interim results :), but that may just be because I don't work with international currencies or large corporations. And besides, till I quit coding to V3R2 levels it doesn't much matter. I couldn't use a float field if I wanted to... >Ouch! It's those darned decimal variables that always give >us grief. Us too. <g> (I sure wish Rochester had designed for full operational descriptor support!) >Actually, if you really want this "IsNegative" procedure to >work, I think if you make the parameter a long float value Personally, I don't see much value is this particular example. I was simply trying to show Brian that if he felt it was more readable, that he didn't have to ask for a BIF then wait for it. I'm a big fan of subprocedures in general -- they can really add lots of readability to code when named properly. And make life alot simpler in terms of code reuse. Service programs are great. But regarding long floats -- is conversion to them an "expensive" operation? I'm assuming (bad idea) it is much more so than decimal alignment of other packed fields, or conversion of zoned or integers. I suppose a function like IsNegative() would not be likely to be used heavily enough to even care to benchmark the difference between using a 30P 9 const argument and a long float. Doug +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.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.