[Tfug] Developer question

[jblais]

> -----Original Message-----
> From: tfug-bounces at tfug.org [mailto:tfug-bounces at tfug.org]On Behalf Of
> Bexley Hall
> Sent: Friday, July 06, 2007 2:52 PM
> To: Tucson Free Unix Group
> Subject: Re: [Tfug] Developer question
>
>
> Yes, but, as with my comments to Joe (as well as my
> original stipulations re: executing code), this
> forces the table to be in a DATA segment.  This
> means there is *some* run-time cost to initializing
> it (even if it only appears as a "start up cost"...
> ever wonder why so many systems take SO long to start
> up?  :>).  And, it means I have to pay for the
> table's space, *twice* -- once for the nonvolatile
> image (i.e. the definition and code to initialize it)
> and once for the run-time/volatile image (i.e. in
> RAM someplace).
>
> I guess the "load from disk" paradigm is too heavily
> ingrained, here.  :-/  Imagine a device *without*
> a disk and where every *byte* (not MEGAbyte) of RAM
> has a co$t associated with it...
>


I's been a long time but -- hwow about with ASM statements -- somehow

C/C++ should be able to handle them -- I haven't thought the whole thing
through, and I've definately forgotten the syntax, and am too lazy to figure
it out but...


ASM LABEL   _START_COLORS_
ASM LABEL   _BLUE_
ASM DATA    "BLUE"
ASM LABEL   _GREEN_
ASM DATA    "GREEN"
...

I'm not shure how to associate the labels with enums

joe ?