kdelibs/kdeui

Ingo Klöcker ingo.kloecker at epost.de
Sun Apr 21 18:57:00 BST 2002


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

On Sunday 21 April 2002 19:22, Dirk Mueller wrote:
> On Son, 21 Apr 2002, Lubos Lunak wrote:
> > > Yes, does that prevent people from committing broken code? no.
> > > When we change the default to --enable-warnings, those people who
> > > care about the 1% performance penality will immediately switch to
> > > --disable-warnings and continue committing broken code.
> >
> >  But such people will be different from those who now don't see the
> > warnings - those who don't see the warnings now often don't know
> > how to turn it on or even that they can turn it on, while people
> > who will use --disable-warnings and commit code with warnings are
> > ... well ... @#%#!
>
> Yes, you get the problem :-) Its the same with the recommendation to
> use --enable-debug, and still, how many developers use --enable-debug
> ?

Maybe you should make --enable-debug=full the default for people 
compiling from cvs (which developers usually do). I don't know if it's 
easily possible to differentiate between cvs builds and normal source 
builds though.

Regards,
Ingo

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8wv1sGnR+RTDgudgRAsldAJ9hy5Q3SVjXDi31k64JlStso0dnmgCguU78
lflPjVkGS7yp8VCSl5mraJQ=
=C4ex
-----END PGP SIGNATURE-----




More information about the kde-core-devel mailing list