Hi Kiste, I had a randomly & quick overview of your lib and noticed you used quite common variable names, such "minutes", "hours", "month", etc... These can conflict with existing library or, more probable, with some user code. Same for proc/func.
Usually we have to prefix with lib name to avoid (eg. bigcal_month, bigcal_hours, ...). But we can also use new jalv2 "record". This can be nice to group namespace related variable. I had the same issue recently and used them. Code IMHO is more readable, and from footprint is mostly the same (if not the same). Unfortunately, proc/func can't be grouped in a record (well we'd be closed to OOP :)) Namespaces in jalv2 can be naughty and usually require extra work to avoid conflicts. It'd be nice to select the namespace code would live in... No ? Cheers, Seb 2012/4/12 <[email protected]> > Revision: 3024 > Author: [email protected] > Date: Thu Apr 12 08:05:01 2012 > Log: New, extended calendar library > http://code.google.com/p/**jallib/source/detail?r=3024<http://code.google.com/p/jallib/source/detail?r=3024> > > Added: > /trunk/include/jal/big_**calendar.jal > /trunk/sample/16f688_big_**calendar.jal > > -- > 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 jallib+unsubscribe@** > googlegroups.com <jallib%[email protected]>. > For more options, visit this group at http://groups.google.com/** > group/jallib?hl=en <http://groups.google.com/group/jallib?hl=en>. > > -- Sébastien Lelong -- 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.
