On Sat, Jun 9, 2012 at 1:54 AM, Thiago Macieira
wrote:
> On sábado, 9 de junho de 2012 01.42.21, 1+1=2 wrote:
>> > Do we need this for every file, or is one entry in qglobal.h enough?
>>
>> One entry in qglobal.h is enough.
>
> It's also weird. The option should be the input charset, not the execu
vs2010 is OK, but vs2012 RC failed, I just want to try win32-msvc11.
2012/6/10 Thiago Macieira :
> On domingo, 10 de junho de 2012 01.53.10, techabc wrote:
>> It seems that no more alpha 2 comes to the world.
>> I wish upcoming beta would full pass compile of Visual Studio 2010 RC.
>
> What do you
On sábado, 9 de junho de 2012 21.42.55, André Pönitz wrote:
> My gut feeling says there is a sweet spot at 16 byte object size,
> with direct pointer to the raw data, and size member and some
> sensible use of the extra bits.
Agreed, but it's 16 bytes on 64-bit architectures. On 32-bit ones, it wo
On Sat, Jun 09, 2012 at 05:45:01PM +0200, Thiago Macieira wrote:
> [...] - André requested that the size member be moved away from the
> header into the main class body itself. I haven't done that yet and
> I'm not sure I should. It would be major surgery for something that we
> haven't proven yet.
On domingo, 10 de junho de 2012 01.53.10, techabc wrote:
> It seems that no more alpha 2 comes to the world.
> I wish upcoming beta would full pass compile of Visual Studio 2010 RC.
What do you mean by 2010 RC? Why don't you use the released version?
I compiled with VS 2010 and it worked fine.
-
It seems that no more alpha 2 comes to the world.
I wish upcoming beta would full pass compile of Visual Studio 2010 RC.
2012/6/3 :
> It's not wrong and it doesn't really matter. Once MSVC starts to differ from
> the VC version, in the sense that they are not connected, then we can discuss
> ch
On sábado, 9 de junho de 2012 19.31.09, Olivier Goffart wrote:
> Then, one can put back 'alloc' in QArrayData
It's not worth it. It increases the size of the 32-bit structure and leaves us
at a weird boundary on 64-bit ones. 32 bytes is actually good.
--
Thiago Macieira - thiago.macieira (AT) int
On Saturday 09 June 2012 19:19:41 Thiago Macieira wrote:
> On sábado, 9 de junho de 2012 19.15.09, Olivier Goffart wrote:
> > I suggest re-ordering the offset in order to avoid padding.
>
> It doesn't help.
>
> > struct Q_CORE_EXPORT QArrayData
> > {
> >
> > QtPrivate::RefCount ref;
> >
On sábado, 9 de junho de 2012 19.15.09, Olivier Goffart wrote:
> I suggest re-ordering the offset in order to avoid padding.
It doesn't help.
> struct Q_CORE_EXPORT QArrayData
> {
> QtPrivate::RefCount ref;
> uint flags;
> qptrdiff offset; // in bytes from beginning of header
> in
On Saturday 09 June 2012 17:45:01 Thiago Macieira wrote:
> Hello
>
> Moving the discussion from the series of patches I've begun on Gerrit to the
> ML.
>
> tl;dr: all I wanted was to add the prepend optimisation to QVector so I
> could work on QList. Then João told me of a request by Tor Arne abo
Hello
Moving the discussion from the series of patches I've begun on Gerrit to the
ML.
tl;dr: all I wanted was to add the prepend optimisation to QVector so I could
work on QList. Then João told me of a request by Tor Arne about letting
QString have a "notify of destruction" function. So I change
On sábado, 9 de junho de 2012 01.42.21, 1+1=2 wrote:
> > Do we need this for every file, or is one entry in qglobal.h enough?
>
> One entry in qglobal.h is enough.
It's also weird. The option should be the input charset, not the execution
charset.
--
Thiago Macieira - thiago.macieira (AT) intel.c
On Fri, Jun 8, 2012 at 1:15 AM, wrote:
> Do we need this for every file, or is one entry in qglobal.h enough?
>
One entry in qglobal.h is enough.
> As another solution, are there any compiler flags one can set to tell MSVC
> about the input encoding? If yes, we can simply add that to the qmake.
13 matches
Mail list logo
