|
Jon summarizes my take on it. If all of the other data in the program
(standalone fields, constants, data structure subfields) can be INZ'd on a
D-spec, why would I want to do something else for an array?
Most of the suggestions seem to be to initialize the values in strings and
use the overlay technique. Since that seems to be the most widely offered
suggestion, I would take that to be the current "best practice".
The applicaiton that I'm using has a known, finite, practically guaranteed
set of values that won't change ('footer', 'header' in my example, another
is 'top', 'bottom', 'left', 'right'). For simple data like that, I want it
hard-coded into the D-specs, no need to load it from a database.
I hoped that something like the following would have been possible
(apologize in advance if the formatting is thrown off, it lined up when I
typed it in).
D Array1 1 dim(4) inz('fFhH')
D Array2 6 dim(4) inz('footer+
D footer+
D header+
D header')
Thanks for all of the suggestions and follow-up.
Craig Pelkie
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.