> I updated svn and found the files, I am sorry you still had to change
> things in my file
> I thought I changed the lcd_st7026 to jallib structure.

It's ok, no problem.

> I know you have a program to check the libs, and I can find it in the
> tool map, but how does it work?

Go to "tools" then:

python jsg_validator.py <the_file_to_validate>

Of course it won't give any information about where the file should be store. 
BUT: this script should be run, ideally before committing the code, so 
lib/sample/... committed is validated to be "jallib style guide" (JSG) 
compliant (that's a start, that's important).

Tell me if you have problem to run it.

> I could not find the –i compiler option in the jalopts document, what
> is it doing?

  jalv2 --help 

See "-include" option. For example:

  jalv2 -i board_16f877a_dwarf .jal i2c_test_l0.jal

The compiler, before actually compile i2c_test_l0.jal, will first include 
board_16f877a_dwarf .jal. This can be used as a smart way to seperate the 
logical code from the chip definition/configuration.

>
> In my opinion a test file and I sample are the same thing, both should
> be a main file being able to compile and work.

After a (long) discussion, tests and samples aren't the same. Samples are to 
show basic usage of a lib. Tests are designed to heavily test a lib, every 
func/proc, at their limit.

(Joep, correct me if I'm wrong... :))

> I understand your point but I also understand Joep’s point, I also
> think its tricky to give samples
> or test files the same name as the lib even if a good map structure is
> separating them.

Yes, they shouldn't have the same name.

> anyway this is only my opinion, what ever you all do is fine with me.

Thanks for your feedback !


Seb
-- 
Sébastien LELONG
http://www.sirloon.net
http://sirbot.org

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