Hi Seb, If you think prefixes shouldn't be added, you can skip them. The rule is "try to think globally, if other people write a lib closed to yours will there be collisions ?". I noticed "year" was too generic and could collide with user code.
Yes, this came from trying to keep some sort of compatibility with "calendar.jal". Using records, it all looks very much nicer, but it does cost some bytes, both RAM and code. As for nitpicker, I'm wondering why you don't validate before comitting. Oh, nitpicker is more some kind of title, not an insult. I did not validate, because I thought I was perfect and couldn't do wrong anyway. And, because I never cared to find out if validation-at-home is possible :-D Maybe you don't have all the python stuff to do so ? For convenience (aand as a fun exercise) I'll try to setup a online tool to validate jallib files. I know python. It's a dangerous animal. Or, if it's Monty, it's very funny. :-D But if you're setting up an online validator, it might well be that I use it occasionally. 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.
