On Saturday 11 April 2015 14:57:39 René J.V. Bertin wrote:
> On Wednesday April 08 2015 13:37:09 Salovaara Akseli wrote:
>
> Hi,
>
> I see I'm being cited as "René J.V. Bertin" (commit
> eb55d48d1035d06408ffe73696223464957aa71d) which means I once more ran
> across a website that doesn't handle
On Friday 10 April 2015 15:59:06 Olivier Goffart wrote:
> On Friday 10. April 2015 13:38:55 Simon Hausmann wrote:
> > Yes, over time we will accumulate cruft. We must indeed be very careful
> > what we put into public header files.
>
> A possibility would be to put them in a
>
> #if Q_DEPRECATED_
On Wednesday April 08 2015 13:37:09 Salovaara Akseli wrote:
Hi,
I see I'm being cited as "René J.V. Bertin" (commit
eb55d48d1035d06408ffe73696223464957aa71d) which means I once more ran across a
website that doesn't handle input from an OS X client appropriately. That
should be "René", of cou
On Friday 10 April 2015 14:06:18 André Somers wrote:
> Marc Mutz schreef op 10-4-2015 om 13:29:
[...]
> > For one, you're not supoosed to inherit from value classes. For
> > another... Oh, I think that's enough reasons :)
>
> That a religious argument instead of a technical one.
Avoiding undefine
On Thursday 09 April 2015, Thiago Macieira wrote:
> On Thursday 09 April 2015 11:20:30 Frank Osterfeld wrote:
> > > My vote obviously goes to allowing them.
> >
> > I had to fix includes when building client code with 5.5 branch (coming
> > from 5.4.1), so this is an actual issue right now, not ju
I think that would be a good compromise.
Simon
Original Message
From: Olivier Goffart
Sent: Friday, April 10, 2015 15:56
To: development@qt-project.org
Cc: Hausmann Simon
Subject: Re: [Development] Are SiCs through #include cleanups considered
acceptable?
On Friday 10. April 2015 13:38:55 S
