[vtk-developers] vtkNew compile error

[Marcus D. Hanwell]

That sounds good, it seems to me that we should ensure that this is added to
VTK before we branch. Brad, do you want to do the honors? I would love to be
able to use this freely in tests and classes.

Marcus

On Sat, Mar 20, 2010 at 10:30 AM, Bill Lorensen <bill.lorensen at gmail.com>wrote:

> It worked great in my experiments. I recall I needed to add another
> method to it for some isolated use case. I can't recall right now the
> situation and my repository is not available to me until April1. If
> needed that additional method can be added later. It did not affect
> the current API.
>
> Bill
>
> On Sat, Mar 20, 2010 at 5:47 AM, Marcus D. Hanwell
> <marcus.hanwell at kitware.com> wrote:
> > On Mon, Feb 1, 2010 at 11:59 AM, Bill Lorensen <bill.lorensen at gmail.com>
> > wrote:
> >>
> >> Sounds good to me. We can address those stream issues at a later date
> >> if need be.
> >>
> >> On Mon, Feb 1, 2010 at 10:53 AM, Brad King <brad.king at kitware.com>
> wrote:
> >> > Bill Lorensen wrote:
> >> >> I think vtkNew would be a good spot to use std::ostream.
> >> >
> >> > I started looking into that and it opens a small can of worms.
> >> > In vtkIOStream.h we do several things:
> >> >
> >> > (1) Support the VTK_USE_ANSI_STDLIB option.
> >> > Now that VS6 is gone do we need this option anymore?
> >> >
> >> > (2) Reduces the MSVC warning level for the stream headers.
> >> > We do not want to do this everyplace we include <ostream>.
> >> >
> >> > (3) Provide streaming operators for "long long" if the native
> >> > compiler does not provide them.  Do all our compilers provide
> >> > this now?
> >> >
> >> > While the above issues are worth discussion for VTK as a whole,
> >> > I'd rather not deal with them for introduction of vtkNew<>.
> >> > Let's just use #include "vtkIOStream.h" for now.
> >> >
> >
> > What was the outcome on vtkNew? I think that this would be a great
> addition
> > before we branch. After so much discussion it would also be great to
> > actually add the API we seem to have all settled on.
> > Thoughts? Objections? As far as I can tell everyone involved likes
> vtkNew.
> > Marcus
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20100321/4706e36f/attachment.html>