> > You can, by replacing the device names and saving is as a different file. >
That is, copying a library and modifying it locally ? No, no, no... No way... > > That is ? You want function_device() instead of device_function() ? > > > It is a compromise between device-specific libs and a common API. I like > it, because it also sets some rules for the general API as well. > > Things like: > > read instead of get/pull/receive/etc > send instead of set/write/etc > These rules are valid whatever the naming convention is. Just another point of view about the current naming convention in JSG Files are named as <function>_<device>.jal Then, in the file, whether you want to avoid collision or create a common API, you use either the <function> or the <device> part of the filename to prefix the func/proc/...**** * <device>_<whatever> if you want to avoid namespace collision * <function>_<whatever> if you want to have a common API The rules you talk about are for the <whatever> part. We can be more precise in the JSG. How would you say that ? 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 -~----------~----~----~----~------~----~------~--~---
