Hi,

a very interesting trick can eliminate a lot of overhead. It can be used,
if: the program you write would fit in a code space which is smaller than
the used processor. E. g. you have a program slightly less than 2 kwords,
AND the processor is either 4k or 8k code space.

Now, at the very begin of the program one can set

DEFINE CODE_SIZE 2      ' expected size of program in kwords

and - of course - you should verify whether the compiled program does not
exceed this limit. If not, you won! E. g. I had a program for a 16F876.
The code was before: 1860 words or so, and after: 1454 words, so one can
save almost a quarter of precious program code area.

Regards,
Imre


On Thu, 30 Dec 1999, Fernando wrote:

> Hi,
>
> Please, I think many people would like to learn all tricks: to discover a
> single trick alone usually takes many time.
> Thanks
> Fernando
>
> -----Original Message-----
> From: Dr. Imre Bartfai <root@PROF.PMMF.HU>
> To: <PICLIST@MITVMA.MIT.EDU>
> Date: Quinta-feira, 30 de Dezembro de 1999 6:49
> Subject: Re: Pic BasicPro
>
>
> >Hi,
> >
> >I have been using the PicBasic Pro for a year; I am satisfied with it, as
> >the effectivity is increased enorm. However, there are some tricks one may
> >want to know. If interested, please tell me, and I could make them public.
> >Once again, it is worth using it.
> >
> >Regards,
> >Imre
> >
>
>