Data tables for a software tool

[Ludis Langens]

steve ravet wrote:
> 
> It's more difficult in C to make data structures both packed and
> portable but you can do it, even to the extent of packing bitfields into
> integer fields.

I don't expect to need bitfields.  The data should be mostly 8, 16, and
32 bit data in arrays.  And arrays of arrays.

> It's more common for really large data to be stored in
> a file and manipulated dynamically than to be compiled into the program,
> why did you decide to do it that way?

The data is static.  The program will never change it.  I want it built
into the program to avoid versionitis and missing pieces.

> Compilers and linkers used to
> support overlays for data in the past but not anymore, because code and
> data spaces have gotten much larger.  How much data do you think you are
> talking about?

The data might eventually grow to > 64K.

> You could distribute the data compiler also, assuming it's written in C
> or something portable.

Apple Computer wrote this "data compiler".  Source is not available.

-- 
Ludis Langens                               ludis (at) cruzers (dot) com
Mac, Fiero, & engine controller goodies:  http://www.cruzers.com/~ludis/

----------------------------------------------------------------------------
To unsubscribe from gmecm, send "unsubscribe gmecm" (without the quotes)
in the body of a message (not the subject) to majordomo at lists.diy-efi.org