× 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.



From: Scott Klement

Err... also, I'm not sure that we need a *MAX32KB. Is that just
for compatibility with older releases, or what?

It's for completeness.

You misunderstand. I was asking why we need a *MAX32KB assuming that we
already have a *MAX64KB keyword.

Gotcha.

If you read in context, you'll see that I was (wrongly) removing one bit of
precision in general. I have never used a 32KB field, much less a 64KB
field, so was unaware that the size restriction had been moved up to 64KB.
Thus, I would stick now with *MAX64KB, *MAX4GB and *MAX256TB were I to use
keywords. However, I prefer the implicit size.

Joe



As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.