On 14 Oct 2008, at 09:44 , Sebastien Lelong wrote: > 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...
This is an age-old tradition in JAL :-) Didn't you exactly the same with pwm1.jal, pwm2.jal, etc. ? > Files are named as <function>_<device>.jal OK. > 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 ? "Either/or" is not a Guide. "Whatever" is not specific enough. device_function is not that clear both inside and outside the library. It reeks of oldskool JAL too. Rob is right dissing "hd44780_line3" names. That is only clear to old guys, who know all chip numbers. Besides, this chip isn't produced anymore, not by Hitachi anyway. Yes, its myriad clones are still available. So that's why I want function_device(). Not just function(), because then we can't use two libs at the same time. *Changing* from one device to another then would only mean search-n- replace the device part in the subroutine names. That is what I meant with: > You can, by replacing the device names and saving is as a different > file. Writing libs that use other specific libs is a bad idea anyhow. I'd like a vote on this, because then I can adapt all my libs and continue with new ones. --- 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 -~----------~----~----~----~------~----~------~--~---
