> Ritchie wrote:
> > I have changed the testing programs for the lcd and rtc libs so that
> > they can be tested with the Repos include files.
>
> At first sight I thought "what are the Repos include files?", but I
> assume you mean the Jallib include files....

Yes I do, from now on I will call them Jallib include files

>
> > I also removed the comment at the beginning af the library files as
> > Seb asked
> > I only noticed that by port definitions the output and input and
> > all_input end all_output assignment are no longer in the include files
> > (libs).
>
> All common constants - like these - are moved to the file chipdef.jal,
> which is included by every (Jallib) device file.

I noticed but used the wrong chipdef.
>
> > I have temperarely add the lines below in the test main file:
>
> > const bit input               = on                   ; this should be
> > in a lib
> > const bit output             = off                   ; this should be
> > in a lib
> > const byte all_input       = 0b_1111_1111  ; this should be in a lib
> > const byte all_output     = 0b_0000_0000  ; this should be in a lib
>
> Did you get compile time errors? If so, you have probably not tested
> with the Jallib device files. Or you did not use the proper chipdef.jal
> (maybe the one of the compiler in stead of the Jallib version)!

As mentioned above I used the chipdef from the compiler directory.
I changed it now and will also change the testing files.

The test files are using the jallib include files and the only errors
I got where
because output and input where not assigned so with the correct
chipdef this is solved..


>
> Regardless if you made this mistake or not, I expect you won't be the
> last one using the compiler's chipdef.jal in stead of the Jallib
> version. Maybe better if we change the filename of 'our' version!
>
I think that’s a good idea, its better not using an old name because
than you don’t know if you have the good lib ore not.
Maybe add to all jallib include files “_v2”  like chipdef_v2.jal then
you can immediately see it’s a jallib include file from the repository
and still the name is familiar to everybody.
Its just an idea.


greetz

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