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

List:       kde-commits
Subject:    Re: new_kcm_code: kdelibs/kutils
From:       Frans Englich <frans.englich () telia ! com>
Date:       2004-10-11 19:59:09
Message-ID: 200410112005.31169.frans.englich () telia ! com
[Download RAW message or body]

On Monday 11 October 2004 19:42, David Faure wrote:
> On Monday 11 October 2004 21:44, Frans Englich wrote:
> > On Monday 11 October 2004 19:29, Frans Englich wrote:
> > > CVS commit by englich:
> > >
> > > Small cleanups:
> > > - Forward port win32 merge
> > >
> > > - Make reportError public, needed by KCModuleProxy
> >
> > I have a question:
> >
> > The binary compat doc:
> > http://developer.kde.org/documentation/library/kdeqt/kde3arch/devel-binar
> >ycompatibility.html
> >
> > says this; "The only compiler affected by this, that we know of, is
> > MSVC++, and KDE doesn't compile on Windows anyway," about changing scope
> > of methods. Since we support now MSVC++, it renders that false, right? In
> > other words, ok to commit attached?
>
> Wrong - then you have to change the parag above,  i.e. to tell people that
> it's not ok to change the scope of methods.

Ok, I find it confusing what the "this" in "The only compiler affected by 
this, that we know of, is MSVC+" means then.

>
> But at this point, even though some stuff compiles with MSVC++, we don't
> care about preserving binary compatibility there, do we? 

I'm not following, why not? (because KDE doesn't official support that 
platform?)


Cheers,

		Frans

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