From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-04-17 08:39:07
----- Original Message -----
From: "Itay" <itay_maman_at_[hidden]>
> 2) Heap allocation of vlarray objects should be prohibited. It seems
> simple problem with a simple solution (having a private new/delete
> operators) but there might be side-effects/portability-effects which I
> not thinking of.
Well, it doesn't really work. A vlarray can always be embedded in
another heap-allocatable class as a member. That's a much more likely
scenario than "new vlarray<double>;", IMO.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk