From: Maarten Kronenburg (M.Kronenburg_at_[hidden])
Date: 2006-05-19 10:32:28
Yes, there will be an abstract integer_allocator class
with allocate(), reallocate() and deallocate() member
functions, so that the user can provide memory
management functions by deriving it.
"Rene Rivera" <grafik.list_at_[hidden]> wrote in message
> Bronek Kozicki wrote:
> > Maarten Kronenburg wrote:
> >> Currently I'm working for LWG on a spec
> >> for tr2 for an infinite precision integer, which is
> >> almost finished.
> > I hope it's not too late for implementation suggestion - I'm familiar
> > similar attempt  and what threw me away was aggressive use of heap.
> > possible to employ technique similar to "small string optimization",
> > when number of bytes stored is below some treshold (presumably set in
> > preprocessor), it will not be allocated from heap, but instead employ
> > fixed buffer inside the number object itself?
> Which brings up, again, the issue of control over how such an infinite
> integer class interacts with memory
> Maarten, do you plan on addressing such issues in your updated proposal?
> -- Grafik - Don't Assume Anything
> -- Redshift Software, Inc. - http://redshift-software.com
> -- rrivera/acm.org - grafik/redshift-software.com
> -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
> Unsubscribe & other changes:
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk