> > Writing a temperature to the screen, depending on a given word, with say > 0.01k as LSB is fine. Writing a temperature to the screen and pulling this > temperature from another lib is not fine. This way you can't re-use the > library anymore for another sensor. > > Writing formatted output to a "device" is good, because device can be a > parallel LCD, a serial LCD or a terminal. > Writing formatted output to a specific LCD is bad, even when using the > specific library. > > Again, have a look at format.jal and print.jal to how it is done. Rob saw > the light too. >
If I understand you correctly, writing libs which use other libs, in a bad design way, is bad. When it is a nice design, it's good. So, yes, I agree.... More seriously, I really don't why we shouldn't build libs over other libs (of course, obviously, if it's done right). Your example about device libs, format.jal and print.jal is not an example of this, I can't see any "include" in them. They abstract the device, that's all (and that's good). What I mean is: -- file low_level_lib.jal -- ; some jal code, low level, I dunno -- file high_level_lib.jal include low_level_lib.jal ; now build a new interface (or whatever you want) ; on top of low_level_lib. Seb --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
