diff options
| author | Max Horn | 2005-01-01 18:56:03 +0000 |
|---|---|---|
| committer | Max Horn | 2005-01-01 18:56:03 +0000 |
| commit | c418282ec724d01e37b13f7372aa2d6b48f6cbe2 (patch) | |
| tree | cf4f63039f62179b47d47aaeb2ee032bc22e4523 | |
| parent | f52be9df681358564991e0988bf70160970104ad (diff) | |
| download | scummvm-rg350-c418282ec724d01e37b13f7372aa2d6b48f6cbe2.tar.gz scummvm-rg350-c418282ec724d01e37b13f7372aa2d6b48f6cbe2.tar.bz2 scummvm-rg350-c418282ec724d01e37b13f7372aa2d6b48f6cbe2.zip | |
One day I wanna switch to STL. Really
svn-id: r16403
| -rw-r--r-- | TODO | 3 |
1 files changed, 3 insertions, 0 deletions
@@ -122,6 +122,9 @@ General we set when the application should be quit (e.g. when an EVENT_QUIT is received). This is useful if multiple levels of event loops have to be ended * Fix the Map<> template, make it more robust; maybe use a red-black tree? +* Instead of the above, consider switching everything over to the STL. + Maybe a little bit more overhead, but we get instant access to a full-featured + and well-tested code base, with everything we need. * Make some generic "EventLoop" API/class which all backends and the GUI use. Initially this would just call the backend poll_event() etc. methods. But eventually the EventLoop object(s) could be made by the backend. |