On 15 Oct 2008, at 09:41 , Sebastien Lelong wrote: > > The JSG is not consistent: > >> procedures and functions must be named as: >> >> * <function>_<whatever> if you want to have a common API > > is not the same as: > >> All external names (of global variables, constants, procedures and >> functions available to application programs) must start with a >> prefix unique to the library. > > > because "function" can't be (and shouldn't be) specific to a library > > If all vars, consts, procs, funcs in a library start with > "blabla_", don't we have a prefix unique to the library ? We do. It is neither a function nor a device.
> As I said a previous post today, the main confusion seems to come > from the meaning of "function". You consider function as "get", > "read", "write", etc... I consider function as "lcd", > "temperature", "i2c", "serial", etc... Maybe, for what I mean, > "device_family" should be better. Both are functions. Methinks that the device specific part should be as descriptive to the device as possible, like chip numbers or _hardware / _software for a serial lib. --- 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 -~----------~----~----~----~------~----~------~--~---
