array in constant?

[Bruce]

LOOKUP a,[1,2,3,4,5,6,7],b.

a & b would be byte variables. a = the index pointer. b = the byte variable
the constant value from the table is placed in.

a = 1
LOOKUP a,[1,2,3,4,5,6,7],b

b now = 2.

This creates a constant array in ROM similar to const char a[]={1,2,3,4,5,6,7};
in C where b=a[1].

[SpiritHunter]

this means that i can put
LOOKUP A,[.......],B

but how can i refer to the A later on?

eg. lookup a,[ 1 2 3 ],b

den how can i do like x= a[1] + a[2] ?

[Bruce]

If you need x= a[1] + a[2] then you'll need to create a standard array of
RAM variables.

Or do something like this;

Main:
     a = 1
     GOSUB GetConst
     X = b
     a = 2
     GOSUB GetConst
     X = X + b ' now X = a[1]+a[2]
     GOTO Main

GetConst:
     LOOKUP a,[1,2,3,4,5,6,7],b
     RETURN

[SpiritHunter]

thanks alot bruce, i think i understand already. will try out 2moro.

[SpiritHunter]

wow.. thanks.... o ya... 1 more question... how many constant can i write in a single bracket? and... is there a problem if i write like this?

LOOKUP a,[1,2,3,4,5,6,7
,b

[SpiritHunter]

wow.. thanks.... o ya... 1 more question... how many constant can i write in a single bracket? and... is there a problem if i write like this?

LOOKUP a,[1,2,3,4,5,6,7
,8,9,10],b

[Acetronics2]

how many constant can i write in a single bracket? and... is there a problem if i write like this?

LOOKUP a,[1,2,3,4,5,6,7
,8,9,10],b

Hi, SH

Will 255 for a 16F series and 256 for a 18F series be enough ??? ( LOL !!!)

...

Note this type of array takes a lot of room ( like with assembler ... 1 prog line per value + 1 ) and you might think at it when choosing your PIC ...

PbP doesn't deal so well with room for this function ... and lots of room is lost with big lookup tables !!!

Alain

[SpiritHunter]

Hi, SH

Will 255 for a 16F series and 256 for a 18F series be enough ??? ( LOL !!!)

...

Note this type of array takes a lot of room ( like with assembler ... 1 prog line per value + 1 ) and you might think at it when choosing your PIC ...

PbP doesn't deal so well with room for this function ... and lots of room is lost with big lookup tables !!!

Alain

? 255 only? i am thinking of at less 500... as i need to bit map all the char in ascii which is at less need 101x5

ya.. i know it takes alot of memory. and i have chosen 16F877A to do the job. i hope 8k is enough for the constants, I2C and a serial communication... if not enough, then i am in big troble.. haha...

so... 16F877A can only allocate 255 in 1 lookup table? if so, den i need to separate the bit map codings.