On 30 Apr, 2012, at 22:13 , ext Thiago Macieira wrote:
>>> Still, I meant my own task: since these are API-level considerations, I
>>> was and still am under the impression that they are needed by beta time.
>>
>> I'm not sure what you mean by this.
>
> This is what answers the "now" part. The c
On 30 Apr, 2012, at 21:07 , ext bradley.hug...@nokia.com wrote:
> No, I'm not rebuilding just the platform plugin(s), this has to do with all
> of qtbase (mostly). I will double check this though, since things are
> constantly changing everyday. The situation may have improved (but that
> doesn'
On Mon, Apr 30, 2012 at 10:13:54PM +0200, Thiago Macieira wrote:
> This is what answers the "now" part. The changes I'm making, like the
> QRegExp one and these deprecation settings, are changing the API that
> we expose to users. As such, I understand that they need to be done,
> ready and tested
On Monday, April 30, 2012 22:36:41 Olivier Goffart wrote:
> On Monday 30 April 2012 19:55:25 lars.kn...@nokia.com wrote:
> > On 4/30/12 9:07 PM, "ext bradley.hug...@nokia.com"
> > >> Peraps we could add back the const overload, but as deprecated?
> > >
> > >Too late now. Change is already in qtbase
On Monday 30 April 2012 21:34:45 lorn.pot...@nokia.com wrote:
> On 01/05/2012, at 12:07 AM, ext Thiago Macieira wrote:
> > On sexta-feira, 27 de abril de 2012 23.02.58, Thiago Macieira wrote:
> >> Just a notice to all devs:
> >>
> >> Since 0df1c9f1fa04c06d6105de3f312c6c752a58ad70 integrated on Wed
On 01/05/2012, at 12:07 AM, ext Thiago Macieira wrote:
> On sexta-feira, 27 de abril de 2012 23.02.58, Thiago Macieira wrote:
>> Just a notice to all devs:
>>
>> Since 0df1c9f1fa04c06d6105de3f312c6c752a58ad70 integrated on Wednesday, all
>> Qt modules have deprecation warnings enabled now. That
On segunda-feira, 30 de abril de 2012 22.36.41, Olivier Goffart wrote:
> > I think most of them were related to qimage.h producing warnings (unless
> > you were using gcc 4.6 or 4.7).
>
> Ah, that could be.. then those will dispear when we start to build without
> deprecated function I suppose.
Un
On Monday 30 April 2012 19:55:25 lars.kn...@nokia.com wrote:
> On 4/30/12 9:07 PM, "ext bradley.hug...@nokia.com"
>
> wrote:
> >On Apr 30, 2012, at 8:50 PM, ext Olivier Goffart wrote:
> >> On Monday 30 April 2012 17:57:46 bradley.hug...@nokia.com wrote:
> >>> On Apr 30, 2012, at 7:19 PM, ext Thia
On segunda-feira, 30 de abril de 2012 19.55.25, lars.kn...@nokia.com wrote:
> Ideally things such as the deprecated warnings should not be enabled until
> someone went through things locally and made sure the amount of warnings
> doesn't drown everything else. Let's please do this the next time.
I
On segunda-feira, 30 de abril de 2012 19.00.31, bradley.hug...@nokia.com
wrote:
> But you're missing my point. I don't think anyone should be doing them. I
> don't think now is the time to have a lot of "low-hanging fruit" changes
> being pushed into to all the modules.
See below.
> The amount of
On 4/30/12 9:07 PM, "ext bradley.hug...@nokia.com"
wrote:
>
>On Apr 30, 2012, at 8:50 PM, ext Olivier Goffart wrote:
>
>> On Monday 30 April 2012 17:57:46 bradley.hug...@nokia.com wrote:
>>> On Apr 30, 2012, at 7:19 PM, ext Thiago Macieira wrote:
On segunda-feira, 30 de abril de 2012 16.58.0
On Apr 30, 2012, at 8:50 PM, ext Olivier Goffart wrote:
> On Monday 30 April 2012 17:57:46 bradley.hug...@nokia.com wrote:
>> On Apr 30, 2012, at 7:19 PM, ext Thiago Macieira wrote:
>>> On segunda-feira, 30 de abril de 2012 16.58.08, bradley.hug...@nokia.com
>>>
>>> wrote:
Seriously? What a
On Apr 30, 2012, at 8:43 PM, ext Thiago Macieira wrote:
> On segunda-feira, 30 de abril de 2012 17.57.46, bradley.hug...@nokia.com
> wrote:
>> When faced with two options, 1) fix deprecated warnings or 2) continue work
>> to restore Qt 4 behavior in the platform plugins, I'm going to say we
>> s
On Monday 30 April 2012 17:57:46 bradley.hug...@nokia.com wrote:
> On Apr 30, 2012, at 7:19 PM, ext Thiago Macieira wrote:
> > On segunda-feira, 30 de abril de 2012 16.58.08, bradley.hug...@nokia.com
> >
> > wrote:
> >> Seriously? What about my comment (plea) to revert the change that enabled
> >>
On segunda-feira, 30 de abril de 2012 17.57.46, bradley.hug...@nokia.com
wrote:
> When faced with two options, 1) fix deprecated warnings or 2) continue work
> to restore Qt 4 behavior in the platform plugins, I'm going to say we
> should be doing 2) and not do 1) at all (since there will be disrup
On Apr 30, 2012, at 7:19 PM, ext Thiago Macieira wrote:
> On segunda-feira, 30 de abril de 2012 16.58.08, bradley.hug...@nokia.com
> wrote:
>> Seriously? What about my comment (plea) to revert the change that enabled
>> these warnings? As I mentioned before (and others in my team), these
>> warn
On segunda-feira, 30 de abril de 2012 16.58.08, bradley.hug...@nokia.com
wrote:
> Seriously? What about my comment (plea) to revert the change that enabled
> these warnings? As I mentioned before (and others in my team), these
> warnings are hurting more than helping, and our time is much better sp
On Apr 30, 2012, at 4:07 PM, ext Thiago Macieira wrote:
> On sexta-feira, 27 de abril de 2012 23.02.58, Thiago Macieira wrote:
>> Just a notice to all devs:
>>
>> Since 0df1c9f1fa04c06d6105de3f312c6c752a58ad70 integrated on Wednesday, all
>> Qt modules have deprecation warnings enabled now. That
On sexta-feira, 27 de abril de 2012 23.02.58, Thiago Macieira wrote:
> You should not ignore them. You should use the replacement functions /
> classes.
One more thing: if you see a qMalloc, qRealloc or qFree in a public header,
please move the code to a .cpp. Or at least leave a // ### FIXME so w
On 4/30/12 4:10 PM, "ext Giuseppe D'Angelo" wrote:
>On 30 April 2012 15:07, Thiago Macieira wrote:
>> On sexta-feira, 27 de abril de 2012 23.02.58, Thiago Macieira wrote:
>>> Just a notice to all devs:
>>>
>>> Since 0df1c9f1fa04c06d6105de3f312c6c752a58ad70 integrated on
>>>Wednesday, all
>>> Qt
On 30 April 2012 15:07, Thiago Macieira wrote:
> On sexta-feira, 27 de abril de 2012 23.02.58, Thiago Macieira wrote:
>> Just a notice to all devs:
>>
>> Since 0df1c9f1fa04c06d6105de3f312c6c752a58ad70 integrated on Wednesday, all
>> Qt modules have deprecation warnings enabled now. That means that
On sexta-feira, 27 de abril de 2012 23.02.58, Thiago Macieira wrote:
> Just a notice to all devs:
>
> Since 0df1c9f1fa04c06d6105de3f312c6c752a58ad70 integrated on Wednesday, all
> Qt modules have deprecation warnings enabled now. That means that when you
> build your module, you'll get warnings abo
Just a notice to all devs:
Since 0df1c9f1fa04c06d6105de3f312c6c752a58ad70 integrated on Wednesday, all Qt
modules have deprecation warnings enabled now. That means that when you build
your module, you'll get warnings about your using of deprecated classes or
function.
You should not ignore them.
23 matches
Mail list logo
