On Jan 8, 8:47 pm, "Le Chaud Lapin" <jaibudu...@gmail.com> wrote:
.... My containers do not use global variables. I am
guessing that you did not say that either, that you mean, if i have one
of my containers with its internal iterators, and Thread A acquires,
does something, and releases, Thread B acquires, does something, and
releases, the next time Thread A comes back, the iterator inside the
container will not be where Thread A left it. ??
If you are saying this, I guess the only thing I can say is that this
never happens in practice.
I do the above quite often in practice, even in single threaded
applications.
A real example:
* Container object contains multiple tracks, each with thousands of
delta-time-stamped musical events.
* The program needs an iterator that holds the current playback
position which is updated based on asynchronous time events.
* The program allows for the user to view the data in a window. The
data viewed is dependent on what the user wants to see.
* While the user is looking at and playing the music, he clicks 'save'.
The function to save the file needs another iterator to go through all
the events and write them to a file.
Therefore two more different iterators are necessary to find the values
to display and save, even in a single threaded application.
container. One I have that, I essentially have as many iterators as I
element, though this is something I do only in rare circumstances. The
[ comp.lang.c++.moderated. First time posters: Do this! ]