> > More seriously, I really don't why we shouldn't build libs over other libs > (of course, obviously, if it's done right). Your example about device libs, > format.jal and print.jal is not an example of this, I can't see any > "include" in them. They abstract the device, that's all (and that's good). > > > You did quite a radical turn on this, but I have to agree. >
??? What radical turn ? About having libs that abstract device, as lcd ? > > What I mean is: > > -- file low_level_lib.jal -- > ; some jal code, low level, I dunno > > -- file high_level_lib.jal > include low_level_lib.jal > ; now build a new interface (or whatever you want) > ; on top of low_level_lib. > > > So no "include" in libraries? It gets my vote. > NO, NO, NO, NO. Here are misunderstanding again... Where do you see that I mean no "include" on libraries ? I say exactly the opposite ! Read again: high_level_lib.jal *includes* low_level_lib.jal. > > This means that the documentation should state what to include. > Look in c02_t6603.jal: > No, no, no, etc... > > -- This library uses the serial_hardware and delay_any_mc libraries. > -- These libs must be included and initialised in the main program before > -- including this one. > > No, no, no, etc... > > Since all libs will be accompanied with a sample, this is not an issue. > No, no, no, etc... 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 -~----------~----~----~----~------~----~------~--~---
