KIO::NetAccess static methods question

[Thiago Macieira]

Em Wednesday 24 October 2007 23:49:33 Andreas Pakulat escreveu:
> Thats only one direction, the Trolls also consider the other direction
> important (though of course not as important as the backwards BC). And
> unless I'm mistaken the forward BC works for 4.2<->4.3, unless of course
> you use 4.3 features.

No.

Qt major releases break compatibility: Qt 3, Qt 4, Qt 5

Qt minor releases retain backwards compatibility: anything compiled in Qt 4.0 
will work in any Qt 4.x; anything compiled in Qt 4.2 will work with Qt 4.3, 
4.4, 4.5, etc.

Qt patch-level releases retain forwards and backwards compatibility: anything 
compiled with Qt 4.3.2 will work with Qt 4.3.0, 4.3.1 and 4.3.3.

By "compatibility" above I mean source and binary compatibility only. The 
levels we consider are:
 source compatibility: source code that compiles will continue to compile
 binary compatibility: code compiled will run against other versions
 behaviour compatibility: you get the same results if you have the same inputs
 bug compatibility: you get the same bugs if you have the same inputs

We try very, very hard to keep behaviour compatibility too. But sometimes it's 
inevitable or things slip through the cracks. The Qt 4.3.2 printing change we 
made for KDE is an example of non-forwards behaviour compatibility (i.e., 
will compile and run, but not work correctly with Qt 4.3.1)

In a couple of places, we also have to maintain bug compatibility. (Cannot fix 
a bug because it would break applications) Thankfully, there aren't many.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20071025/d832aaaa/attachment.sig>