[Qt-interest] What is likely to be in Qt 4.8?

[Thiago Macieira]

Em sexta-feira, 25 de fevereiro de 2011, às 09:52:40, Stephen Chu escreveu:
> Thanks. May I also suggest that for modules/classes/functions that are
> known to be deprecated soon, marks them so in the current, released,
> documentation?

The documentation for the next version is kept up to date. The "what's new" 
page hasn't been written yet, but you can search for new marks of deprecation. 
See also:

http://doc.qt.nokia.com/master-snapshot/obsoleteclasses.html

We can't mark in the current documentation what we intend to deprecate 
because:
a) it's not deprecated in the current version
b) we haven't deprecated yet

We never remove functionality. So when you see "deprecated" it means "this is 
still here, but you should really avoid using it in new code".

> I hate to live through the days when Apple announced deprecation of some
> Carbon APIs in the HEADER files. :(

Apple took a bold decision to not develop an entire framework that people 
depended on. The closest we've ever come to that is to say that we weren't 
including Qt3Support in the new platforms we're adding to Qt.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
Url : http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20110225/219a5a9d/attachment.bin