Accidentally sent this private, sorry. Here for the list again ;-)
> >This is what I thought originally, and it would work in my specific case. But >I'm trying to keep things general (the idea being to submit a new library and >save me ever having to think it through again). It doesn't work if, for >example, you have two interrupt routines which both decide to write to a >variable (one after the other) while it's being read. > >If two routines write to the same location, and there's no coordination of >which has to write when, written data can be overwritten at any time. Just >imagine, routine 2 always writes shortly after routine 1 does. The value of >routine 1 will never be read back, the easiest way then would be not to >implement routine 1 at all. > > >If nobody else jumps in with the blinding bit of inspiration, I'll have a bash >at writing this... > > I wish you success! :-) 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.
