× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. September 2002

Re: BIGINT Field Size

Bob Cozzi wrote:

I agree that (look back) it would have been a good idea to create 1i0
2i0 4i0 and 8i0, however since today we are required to code 10i0 for a
4-byte int, why not add support for the "more clear" declarations? Why
not allow use to migrate towards  1i0 2i0 4i0 and 8i0?  That way when
you add 16i0 it will be all the better.

That only benefits all the trainers and consultants who then have to
explain to confused clients that 1I, 2I, 4I, and 8I refer to number
of bytes, but 3I, 5I, 10I, and 20I refer to number of digits.  You
don't really want that, do you?

Hans

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.