Re: CINT stringstream bug

Hi Axel,

> On 2008-04-01 16:43, Philip Rodrigues wrote:
> > Thanks for the suggestion - I'll try it out. Would it be possible to
> > have CINT generate a warning or an error when attempting to cast an
> > istream to a bool? This would help protect against bugs in users' code.
>
> Problem is: we need to detect the cast from istream to bool so we can issue
> a warning. But if we do that we could as well fix the cast :-) I know it's
> annoying, but the best way for us is to fix it in the new version of CINT:
> we need to fix all the cast operation properly, the istream problem you
> found is just one of them.

Good point - I didn't think of that!

> > By the way, more generally, is there a list anywhere of STL features
> > that are not yet implemented in CINT? I've noticed a few other things,
> > which I think are known issues, but I'd like to be able to check.
>
> There is of course the list of limitations available on the web, linked
> from the CINT site:
> <http://root.cern.ch/viewcvs/trunk/doc/limitati.txt?root=cint>.
>
> Many of the limitations with templates can be solved by creating a
> dictionary for the STL type or by compiling the code using ACLiC (.L
> code.C+) which is the recommended way to work with more complex files
> anyway.

Thanks for the tip.

Regards,
Philip Received on Tue Apr 01 2008 - 22:27:35 CEST