Isn't soemthing some generic programming can solve by either using policies or specialization absed on oeprator selection ?
Maybe yes, maybe no. I personal belief is that this particular approach won't result in a very good library or data structure. I think that there are actually several projects here. One is to implement a bigint from scratch, another is to wrap a different bigint (e.g., gmp). The idea is to produce a variety of integer classes that satisfy different requirements, but not cram them into a single class and/or specializations. A third project might to develop a generic library that encompasses them all. If you provide wrappers for 4 bigint classes, what concepts describe their interfaces? If you end up proposing a bigint class (or two), be specific about your goals. Don't try to be overly general. You won't be able to solve everybody's needs. Andrew Sutton andrew.n.sutton@gmail.com