> Anyway, I was thinking about a way to structure the board file. In this type > of file, you have: > > * PIC conf (clock,...) > * pin definition and other setup for each test > > If we annotate board files with parsable tags in comments (eg. > <conf>...</conf>, <test serial,blink>...</test>), one (me for instance) > could produce a script to parse these blocks and generate samples (eg. pic > conf + blink conf + blink code = blink sample). That could do the job! We could name a group of pin definitions, like led, hd44780 etc. And within the test file, we mention the defintions used. I don't think we have to indicate the end of the definition . Just a statement that a definition starts is okay like: -- definition LED When you (someone ;) parses the test file first, it knows the groups which are relevant. All others (excecpt for the one without a name, at the start) can be removed.
Joep --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
