On 20 Oct 2008, at 20:28 , Joep Suijs wrote: > I see the next options: > (1) lcd_hd44780_clear() > (2) hd44780_clear() > (3) lcd_clear() > > Number 1 is overkill. Once you are working with a hd44780, there is no > need to tell it's a kind of lcd at each interaction.
I agree. Could we somehow differentiate very frequently used external devices from the not-so frequently used? > So this leaves option 2 and 3. > From these, I vote for option 3 until JAL provides means of > function/procedure aliassing (or name spaces support while including). > The main reason is that if we don't, we can't build higher level > libraries that work (efficiently) with different devices of the same > group. 3 is OK with me as well, but I still like the sensor name behind a function like: get_temperature_celsius_tc77() get_temperature_celsius_sht() Can we somehow figure out a numer of functions per device that allows general function calls? Say if we have more than 10, we go for the general name? Then there's still the issue of using two LCD's (rare) or two sensors (less rare). --- ir EE van Andel [EMAIL PROTECTED] http://www.fiwihex.nl Fiwihex B.V. Wierdensestraat 74, NL7604BK Almelo, Netherlands tel+31-546-491106 fax+31-546-491107 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
