- Class Phx::BaseMultiListener< Notifier, Listener, Selector >
- A diagram of the single listener relationship and the "optimized" multi-listener relationship would be helpful here.
- Class Phx::Clock
- Define requirements for the behavior of time. Requiring that time be non-decreasing feels a little strong, but allowing it to be otherwise makes things very difficult for clients -- most, I suspect, will just crash if time ever goes backward.
- Member Phx::Core::systemLog (void)
- systemLog is not actually safe yet -- returns 0 after core is gone.
- Member Phx::Description::Manager::fileDescription (const String &filename)=0
- In the future, we may provide an asynchronous loading facility to allow large resources to be loaded in the background. A listener would be called back to notify the client when the description was available and could be acquired through this method.
- Member Phx::GraphicsEngine::Light::name (void) const
- Add Light attentuation and range
- Member Phx::Lock::Lock (bool recursive=false)
- Adding logging for errors.
- Member Phx::Lock::~Lock ()
- Handle errors by logging information, but don't throw exceptions.
- Class Phx::LockedAccessor< T >
- This derives from LockedPtrInterface. This is a good candidate for optimization, since deriving from PtrInterface would save us several lock operations every time this is used. The BaseListener framework uses this object and incurs 5 lock and 5 unlock operations every time the listener attribute is accessed. With the standard PtrInterface it incurs just 1 of each.
- Class Phx::Module
- Add a "module loader" mechanism to this. Presumably, the loader locates a module by name and simply returns a smart pointer to a Module object.
- Member Phx::NamedInterface::Manager::deleteNamedInterface (const Ptr< NamedInterface > &interface)=0
- Should we require that deferred deletion always be implemented?
- Member Phx::Ptr::operator bool () const
- Implicit conversion to bool is unsafe. There is a safer approach, but it may be non-portable
- Member Phx::ReadWriteLock::ReadWriteLock ()
- Adding logging for errors.
- Member Phx::ReadWriteLock::~ReadWriteLock ()
- Handle errors by logging information, but don't throw exceptions.
Generated on Mon Jul 10 19:45:29 2006 for Phoenix OSFS by
1.4.2