I think this can be a jallib topic, since our work will be affected. > The ultimate goal: use the AST to implement a JALV2 input to C output > translator or 'compiler' which could be targeted to other chips, like > the 34F, 30F, ARM9. > > William
I actually have concerns about this. You can decide weather these things are good or bad. When I talk about C language, I talk about SDCC mostly (since it is an open source language). We would be contributing all of our work to the C world. SDCC does not have the extensive libraries that we have, well, not in an organized fashion. I have recently taken a peek at there contributors form/ mailing list. They do not even have proper licensing discussed as we have with BSD/ZLIB. It has taken us 2 years to get this far with libs, it will take them zero days to get this far? Without looking at / maintaining our own libraries, do you think someone will copy/modify our work, or remove our names from it? hopefully not. We will have 2 copies of each library & sample, one may get modified by a C user. Does this mean the JAL file will be out-dated? How can the C library be converted to jal? I think we should convert C to JAL. In my opinion this should be the first step before we convert JAL to C. Being able to share both ways will benefit both communities. C has more features, so this may be tricky. C to JAL would also allow more types like 34F, 30F, ARM9 as well. Are we going to have to rename Jallib to Jallib+C ? I don't think it is fair to ourselves to convert JAL to C and not the other way around. Matt. -- 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.
