On 11 Oct 2008, at 22:37 , Rob Hamerling wrote:

> Copy!
>
> It seems to me that developers should update/replace only unvalidated
> files and after some time/tests/discussions a new version will replace
> the old validated one.
> Ad 3: Therefore I prefer to specify the include directories explicitly
> and only those which are used by the specific program.


I now realise that if we leave everything in the unvalidated tree,  
and I pass only that to the compiler, my problems are solved too.

So: Copy.

This also means we can *change* the libs, while leaving perfectly  
working copies in the validated tree. I guess some libs will change,  
even after validation and release. The validated tree is than a nice  
backup for working and tested programs.

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