> > > > I guess it's better to provide guidance for people who follow (maybe > > not to close) the book for the second time with jallib in stead of > > bertlib. > > This is exactly what I mean. And by this all the discussions of > constants are closed! :-D We just use Bert's constants...
Well... I hope no ! Some defaults in Bert's libs just don't make sens to me. Discussion about constants/defaults/etc... sounds annoying but clearly are needed. What I want to avoid is a situation in which we could land with jallib + ez mode, where things aren't flexible, where there are too much implicit settings. When you go to school to learn, you still have to invest some time for the basics. When you learn to read, you still have to learn letters first. The idea here is to decide what should be considered as letters. I consider baudrate as a letter (ie. as a basic things to learn when dealing with USART). That's said, if we go with an include/lib, and not a constant, we can provide several ez files, as I already said (Joep, you can't ignore this, we have to forget the EZ constant :)). One (ez_bert.jal ?) could have all the possible defaults there're already in Bert's lib, in addition to classical ez.jal one. A gradient in EZ mode. Let's also remember this: no universal default setting can be applied to everyone. Every projects are differents, and this is why Bert's defaults can't applied everywhere, plus the fact you can't modify them without modifying the lib itself, that we decide to build jallib (amongst other reasons). Seb -- Sébastien Lelong http://www.sirloon.net http://sirbot.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
