[Development] Abandoning the container changes

Thiago Macieira thiago.macieira at intel.com
Thu Jul 5 12:28:58 CEST 2012


On quinta-feira, 5 de julho de 2012 11.28.58, Michael Hasselmann wrote:
> On Thu, 2012-07-05 at 09:04 +0300, Thiago Macieira wrote:
> > Hello all
> > 
> > I think that, despite the potential benefits of the changes, we should not
> > apply them at this time. There are far too many chances for breakage and
> > it's a blatant disrespect for the feature freeze.
> > 
> > The changes are public, though, so we can always retrieve them for Qt 6
> > when we do it in (say) 4 years time.
> 
> I don't know the changes in detail, but would it be possible to
> introduce the container changes under a special namespace instead (think
> std::tr1)?
> 
> Then we could still choose to use them in new code and the transition to
> Qt 6 would be somewhat easier.

We can add them, but I don't see a value in doing that if no one is using 
them. They'll just increase build time.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
     Intel Sweden AB - Registration Number: 556189-6027
     Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20120705/248e7da6/attachment.sig>


More information about the Development mailing list