Hi Kiste, > > And the three samples which I have recently committed (but not sceduled for > release yet) are all tested on real hardware. > I for myself would prefer a few samples that are guaranteed to work from a > whole bunch of samples that are only probably working. Basicaly you are right, this would be the ideal situation. There are however a few issues: - the level of 'guarantee' you persue requires that all samples are to be retested on real hardware before each release of jallib, especially when a new compiler is added. This turns out to be an unreachable goal. - compiletime failure is detected by buildbot, so the risk is runtime failure on a particular device. I expect this is pretty low if the sample is verified to work on at least one device. - multiple, similar sample that are manual maintained have a higer risk of deviation (failure or just not up-to-date).
I guess this is a help vs risk issue: how many people are helped when there is a sample for their specific chip and what is the risk invovled of non-working samples (vs what would happen if the user would try and port a sample to a non-supported chip). What I see is that there are 594 samples for 158 different chips (not counting the basic blink samples). However, there are 74 samples that only run on one device. I guess it is not so obvious to find such a sample when it is not available for your chip and you are not aware of the existence of that sample. In other words: I guess our samples are quite inaccessible. Maybe we should consider to change this, e.g. by: - reducing the number of samples (only one sample per library) and abandon the generation - create a directory which contains one copy of each sample, next to all samples we now supply. - create an index Joep Row Labels Count of Sample 1 74 2 14 3 18 4 4 5 8 6 8 7 6 8 4 9 2 10 14 11 1 13 3 14 1 38 1 Grand Total 158 > > If I have the time I'll have a look at the test/board files, though. > > Greets, > Kiste > > -- > 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. > -- 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.
