I see some similarities with the other discussion... After reading the JSG page, it is not clear to me. Device, function etc with no example. To give one:
lcd_hd44780_clear() is which is <device_group><device><function>, so I have a different definition of function then JSG. I suggest to add examples of files and functions to the jsg page when we have decided on this. The good thing is we seem to agree on <device_group><device> (where device is either a part number or implementation like hw, sw) for file names. Now we get at the tricky part. 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. 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. (okay, we can of course duplicate each higher level library for each base libarary or provide two versions of the base library. Just a matter of some scripts. But the result would be way to many files to pick from if you don't have the overview. So this is not an option.) my 2c Joep --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
