TOP PRIO
--------
* exception/error handling lacking in many methods
	* What strategy? Safe and slow or unsafe and fast?
		Probably best to have the basic class being safe.
		Subclass overrides methods without checking...
	* Catch Bit::Vector error codes and turn them into Ruby exceptions
	* Clean up among errors thrown. Now I use both RangeError, 
	  IndexError and ArgumentError without a clear strategy.
* interface "same" as Ruby std classes (Array et al)
	* get input from Ruby community (ruby-talk?)
	* compare interface to interface of classes in Ruby std lib. 
* semantics of arithmetic ops? Should we expand results to account for carry
  or use the current design of setting a class var?
* extend tests, especially for arithmetic ops

LOWER PRIO
----------
* Ruby-specific docs
* fix so that all methods update carry. For example succ and pred doesn't now
* C-implementations of the stuff in bitvector_extra.rb?
* extract prototypes into .h-file for use from C
* can randomize with prob != 0.5 be optimized?

WELL...
-------
* wrap matrix methods (anybody has a need for them then please drop me a mail)
	* BitMatrix class?
* add cvs ids
