Hi Joep,
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 was thinking the other way: let the test file cleaned from any tags, etc..., and put them in the board file, to let the code as clean as possible. I guess this is the same, since if we (I) parse these files, we (I) can remove obscure tags. > 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 The end of tag is just here to show the end of block. Else, the end of block is detected as soon as there's an empty line (like api doc when parsing comments above functions). This may be quite annoying when writing jal code not to have line break. The coder has to be "free" to organize the code the layout he wants. Don't you think ? Also, for the same reason, we should use a special char, something like @led, @ldc, etc... like javadoc or the like. My pseudo xml tags were just examples, I'm not in favor of using them. 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. Except the first, which can even be generated on the fly, with appropriate clock speed, xtal type, etc... I was wondering if we could also generate board files :) Cheers, Seb --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
