[PicForth] Re: Porting questions

[easlab at absamail.co.za]

>>>>> "JC" == J C Wren <jcwren at jcwren.com> writes:

> JC> What's the scope of work involved in porting PicForth to gforth
> JC> 0.6.2?
> 
Samuel Tardieu wrote:
> Probably not much but tricky. The input system has changed between
> GForth 0.5.x and GForth 0.6.x. If someone submits the patches, I'll be
> happy to integrate them.
> 
Who's going to test them ?
Have we got a test harness ?
Is there any benefit in always chasing the 'latest', imatured/unproven 
   version?
GForth repository seems well archived.
I know of no problem with GForth 0.5.x.

> JC> Next, what about supporting the PIC16F8620 parts?
> 
> Porting to a new platform with the same instruction set ought to be
> very easy. Probably only constant definitions and such. You can look
> at pic16f88.inc to get a taste of what it takes.

It's all about getting the maximum results with the available resources.
Division of labour is a big factor.  
   This is usually understood and not discussed.
Of course if your a school teacher, you're looking for tasks to keep the
kiddies busy.

== Chris Glur.