[Development] Container refactor update
thiago.macieira at intel.com
Tue Jun 19 09:39:45 CEST 2012
On terça-feira, 19 de junho de 2012 09.21.46, Peter Kümmel wrote:
> On 19.06.2012 08:44, Thiago Macieira wrote:
> > Yes, I know about it. No, I did not look at it. I cannot do that because I
> > need to write code of my own. I cannot look at other people's code and
> > submit to the Qt Project under the CLA, unless it's in the public domain.
> You must not read other code?! Then sorry for the link. Hope you could
> everybody convince you haven't clicked on the link, at least when your eyes
> were open ;)
If I read their code and then implement a vector soon after or at the same
time, one could argue that I copied their code onto Qt. That's why I don't do
> > What's more, lock-free is a technique for making thread-safe containers.
> > Qt
> > containers are not meant to be that. And when you say "at some places it
> > uses lock-free", it implies that in other places it doesn't,
> > which means those places use locks and that's not acceptable.
> I don't know what code is thread save. Seems the vector is not, like yours.
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 190 bytes
Desc: This is a digitally signed message part.
Url : http://lists.qt-project.org/pipermail/development/attachments/20120619/ded8b474/attachment.bin
More information about the Development