🚀 go-pugleaf

Bruce wrote:

> Ok I figured this out...
> 
> I needed to dereference the pointer..
> 
> I wonder how come it compiled before?
> 
> (I should probably investigate... B)
> 
> Thanks  again guys...

You probably figured this out already, but just in case <g>

With STLport, the standard library that shipped with BCB6,
vector::iterator was simply a typedef of T *.  With the Dinkumware
library, vector::iterator is a class in its own right, which allows for
stricter type-checking, run time bounds checking, etc.

According to the standard, both are permitted - although there is a
wide (not unanimous) consensus that Dinkumware's way of doing things is
'better'.

Unfortunately, any code that made the assumption that vector (or
string) iterators were raw pointers will break with the new compiler.
However, that code was always 'broken' in the sense that it was not
portable, but relied on an implementation detail of the STLport library.

Small comfort when it is your own code that needs fixing though ;?)

Another change you might find with Dinkumware is that it does a much
better job of isolating std headers, so if you include one standard
header you do not get a lot of others included for free - as
implementation details.  We found a lot of our code relying on
'accidental includes' in the STLport library.  These were comparatively
easy to clean up though.

-- 
AlisdairM(TeamB)