vasile surducan wrote:
> What is easier than to specify: > > T1CON_T1CKPS = 0b10 > > Yes, that's fine but not in assembler. This is Jallib, not PIClist. > I can't rise up to level 3 with my entire code because most of the > time I find all kind of bugs (everything compiles OK but don't work > on my hardware,) ... Did you report these bugs to Kyle? > ... and I don't have time for hunting weird sintax code > or just code bugs or even IDE bugs (both picshell and jaledit ar > crashing very often); that was on jalv04 but not anymore, I let this > pleasure to younger people or to the software guys which loves coding > in pure form. My expectation is finishing at least one step of a > project without infinite headaches. Sorry to hear about your headaches, but how much did you pay for JalV2 and Jallib? So which rights have you to get something changed or repaired? We in Jallib are very well prepared to make necessary changes when there are good arguments, and we have made many changes and additions. But I don't regard 'because I want to write assembler' as a good argument. With Jalv2 there is barely a need to write assembler. As far as I know none of the libs use assembler (except Eur's timer interrupt service routine). Regards, Rob. -- Rob Hamerling, Vianen, NL (http://www.robh.nl/) -- 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.
