After looking at my checkbook about 30 times and hitting my head against the
wall shortly after, I think going with HT is the best way for me long term.
However Gerhard, you did bring up a good idea with the macros and such.  It
might make good business sense for the CCS guys to write up some include file
(filled with macros) to make things slightly more compatable.

Gerhard Fiedler wrote:

> At 11:16 12/30/2001 -0800, Mark Newland wrote:
> >Therefore, I can see my options as follows (someone feel free to add more):
> >
> >2) Buy CCS and write it for easy porting to HT later (that should be FUN,
> >haha!!).
>
> This might be a real option. Well structured code, some standardizing
> typedefs and macros and consistent use of the special features makes this
> easier.
>
> >5) Go into debt and give Don (Hi Don!!) $750 and buy HT (kind of leaning
> >towards this way)
>
> Apparently this is what I did... But I got it cheaper, I was a beta user
> back then :)
>
> >Dale Botkin wrote:
> > > setup_adc(ADC_CLOCK_DIV_32);
> > > setup_ccp1(CCP_CAPTURE_RE);
> > > setup_timer_1(T1_INTERNAL | T1_DIV_BY_1);
>
> Stuff like this, for example, should be possible to handle with macros.
> Even more so if you already do it with macros (that expand to the above) in
> CCS, and then just replace to what the macros expand when moving to a
> different compiler.
>
> ge
>
> --
> http://www.piclist.com hint: The PICList is archived three different
> ways.  See http://www.piclist.com/#archives for details.

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.