Re: New CNC software rev finally done...

Dave, Jon, and the list,

The last time I converted a BASIC program (map program for APRS and
Amateur Radio) to 'C' (OK, 7 years ago), I went through the code,
function by function, wrote a header for each function (subroutine) to
describe it's operation, and then wrote new 'C' functions. It quickly
gave me a compatible (data wise) program base to work from. I DID
prototype each function, and put the main at the start of the file, and
lower routines following!

I'd heard that code converters worked (tried a BASIC to 'C' converter),
but Jon's right, not terribly manageable after that.


Alan KM6VV


Jon Elson wrote:

>
> dave engvall wrote:
>
> > > Alan M wrote:
> > > >>Just curious, why could you have "NEVER gotten this working in
> > > >>plain C"
> > >
> >
> > It is my understanding, but I've never tried it....that writting code in PASCAL getting it debugged then using a PASCAL -> C
> > translator and compiling, using a good C compiler gives very nice and fast code.
>
> Yup, sort of. I've used the P2C converter for some of the small
> programs that generate G-code for simple operations. But, you
> don't want to go in and change the C code later, as some of the
> hackery it does to make the I/O compatible is really wierd!
>
> Jon
>