On Apr 7, 1:19 pm, William <[email protected]> wrote:
> > We can actually do both C and Python for awhile and maybe you'll come > to like Python. > > William I'm still confused as to why this is got anything to do with Jallib or jal. How many 100,000 line programs are there in JAL that need to be ported to C? How many programs or libraries in JAL need ported to C? If it works on 18F why port it to any other chip? If you really need an ARM, x86 or MIPS (PIC32) (forget the other processors mostly and possibly MIPS too) and not an 18F, it's likely you need an OS too. I see little value in porting existing JAL code. I'd see some value in an enhanced JAL, aka JAL3/Handy that has strong types, sets, enums, records, objects (but no pointers, thanks!), user defined types, Modules/Block with export and global options on declarations etc. If it 100% accepts current JAL code. Translated code is a terrible basis for a new project, esp. to C where there is no shortage of Libraries for ARM, MIPS (PIC32) and x86. I've looked at PIC16 C compilers compared with JAL. There is no reason whatsover you would use C on 16F and 18F if you have a Jal programmer and compiler. Of course maybe I have totally misunderstood what the purpose of this is. -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
