Is there a write-biased lock available for boost::shared_mutex?

[rollie]

Is there a type of write lock available on a boost::shared_mutex that will block future read locks until the write lock has successfully obtained the lock and released it? unique_lock seems to still allow shared_locks to be acquired.