Hi Vasile, 2010/4/23 vasile surducan <[email protected]>: > The problem is what Rob will think about it, since > Atmel has at least as many devices as Microchip has....
The blink-example shows the use of DDRB and PORTB, which are register on ATmega processors. They are defined in the C-compiler device files and currently, you can just use them without any effort. In future versions, prototypes might be required but prototypes are much less detail than the actual defintion. They tell DDRD is variable (maybe with type info, in this case byte). The details are handled by C compiler. And it would IMO even be acceptable if there is a generic device file that names all possible ports and the C-compiler rejects use of ports that do not exist on a particular device. So I think we'll end up with a device file (actually: 2, one in C and one in JAL) that support a range of chips. And like you, I'd like to hear Robs view on this. @William & Vasi This is exactly the dilema - go for the functionally best sollution will take quite a lot of effort and the resulting target code will be less efficient. Consolidating the current situation is slightly off that track, but will provide a usable version without tripling the effort so far... 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.
