On 15 Oct 2008, at 07:47 , Sebastien Lelong wrote:

> 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 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.

This means that the documentation should state what to include.
Look in c02_t6603.jal:

> -- 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. 


Since all libs will be accompanied with a sample, this is not an issue.

---
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to