> > Can you define a namespace for: > > > > library files > > > > function_device > > so lcd_hd44780_4.jal, temperature_tc77.jal co2_t6603.jal?
Yes. > > > library procedures > > library variables > > > > variables and procedures follow the same rules, no distinction. For > > both: > > > > device_whatever if you want to avoid namespace collision > > so hd44780_clear(), hd4480_line1(), hd44780_line2(), No because lcd libs are designed so they can substitute. > tc77_read_celsius_sbyte(), tc77_read_raw(), t6603_read_co2_ppm(), > t6603_set_height()? Yes. > Again, JSG: > > Name your pins according to the context, to what your library is > > doing. Client code, ie. users, will have to define those variables > > before actually include your great library. > > I like to name the pins as they connect to the external part, like: Yes this makes, particularly when you follow a schematics. 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 -~----------~----~----~----~------~----~------~--~---
