Main Page Namespace List Class Hierarchy Compound List File List Compound Members File Members Related Pages Examples
The Design of the LoopState Pattern
This is something I came up with on my own, but I'm sure it's been done before. The primary requirement was for a way for one module to get a sequence of data (such as the elements in a container) from another module, with run-time variability in the provider's structure, and with re-entrancy. Secondary requirements were efficiency, type-safety, and ease-of-use for the module obtaining the data. Tertiary requirements were ease of providing data.
Some other approaches: open/read/close (more verbose, slower, not type-safe), STL iterators (no run-time implementation variability), Iterators [like JDK] (more verbose, slower, not type-safe), ...
Home to blindfold. This page generated via doxygen 18.104.22.168 Wed Oct 10 16:40:37 2001.