[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: qt 3
From:       Marc Mutz <Marc.Mutz () uni-bielefeld ! de>
Date:       2001-08-27 12:03:52
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 23 August 2001 16:51, Simon Hausmann wrote:
<snip>
> I don't think we should do that. I'd rather go for disabling
> QT_NO_COMPAT and QT_CLEAN_NAMESPACE for now. That gives far more
> source compatibility and will give us a running system much faster
> (with less work) . (it will enable QList/QDict, etc.)
<snip>

kdelibs header files should really compile under the most restrictive 
QT_... defines _now_, because you have to let the application developer 
decide what defines he wants to use.

the minimus set is IMO:

QT_NO_COMPAT
QT_CLEAN_NAMESPACE
QT_NO_ASCII_CAST
- -and- (kurl.h recently broke that!)
QT_NO_CAST_ASCII


Marc

- -- 
Even though copyright law gives individuals rights such as fair use,
the DMCA and FTAA's proposed anti-circumvention provisions outlaw all
tools that are necessary to exercise those rights, effectively killing
fair use in the digital age.
              -- EFF FTAA Alert:
                 Stop Hollywood Forcing Technology Ban on 34 Countries
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7ilLK3oWD+L2/6DgRApDGAJ9Fiu9gNrA4YKFhyltCFNnIdK0VDgCg9350
qzW/Mgklfix8JklOM9N7k7s=
=bEpy
-----END PGP SIGNATURE-----

[prev in list] [next in list] [prev in thread] [next in thread]