> A grep on 'calendar' gives me: And a grep on "include" and "calendar" gives the same result :-)
There's the library "now.jal" which is probably related to calendar.jal > > I haven't looked very carefully to the differences, but > maybe it is possible to combine the calendar libraries (and > temporary call the old one calendar_deprecated). Another > possibility is to move common code to a calendar_common > library. The common part is a routine which handles overflows from seconds to minutes, hours.... to years. The calendar.jal implementation is a bit cheaper on code, ram and stack, but only works from 2000 to 2099 (it's limited to 2050 now, I have no idea why.) > All calendars will use a time source. Is that an area where > standardisation is desired? Both libs do not care for timing, they rely on some "external machinery" to increment a variable once a second. The libraries "rtc_isr_tmr[0..3].jal" seem to be designed for that job and they use a global variable called "seconds". I'd like the prefix fans to propose a scheme for prefixes on global variables which are to be used in multiple libraries. Greets, Kiste -- 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.
