Re: [Development] Proposal for allowing handling of HTTP redirects in QNAM

2013-12-24 Thread Mandeep Sandhu
>> >> 3. QNetworkReply stores both, the original as well as the final url. > > What about the intermediate ones in a chain of redirects? > Another question that springs to mind is what should the QNetworkReply object returned to the user reflect while the redirects are going on? Eg: What should t

[Development] Werror check for headers causing FTBFS in sparc (cast-align)

2013-12-24 Thread Lisandro Damián Nicanor Pérez Meyer
Hi! I've hitted a FTBFS in sparc while building qtsvg-opensource-src (by enabling the tests): /usr/include/qt5/QtCore/qhash.h:283:45: error: cast from 'QHashData::Node*' to 'QHash::Node* {aka QHashNode*}' increases required alignment of target type [-Werror=cast-align] The full build log c

Re: [Development] [Proposal] Replace size related parameters with size_t

2013-12-24 Thread Thiago Macieira
On terça-feira, 24 de dezembro de 2013 19:26:27, Kurt Pattyn wrote: > QString, QByteArray, QList, aso often use sign integers to store sizes, > indexing, aso. This often leads to signed/unsigned mismatches and is not > really according standard practice. No, they don't. That's why we use int ever

Re: [Development] [Proposal] Replace size related parameters with size_t

2013-12-24 Thread Yves Bailly
On 24/12/2013 19:26, Kurt Pattyn wrote: > QString, QByteArray, QList, aso often use sign integers to store sizes, > indexing, aso. > This often leads to signed/unsigned mismatches and is not really according > standard practice. > Also, this restricts the indexes, sizes, aso to 32-bit. 31-bit ac

[Development] [Proposal] Replace size related parameters with size_t

2013-12-24 Thread Kurt Pattyn
QString, QByteArray, QList, aso often use sign integers to store sizes, indexing, aso. This often leads to signed/unsigned mismatches and is not really according standard practice. Also, this restricts the indexes, sizes, aso to 32-bit. One solution to resolve the signed/unsigned mismatch is to c

Re: [Development] Qt 5.2.0 compilation fails on ArchLinux [SOLVED]

2013-12-24 Thread Wilhelm Meier
Hi, finally I solved this issue: ArchLinux defaults to Python3! Setting up a Python2 virtual environment solved the errors! Merry Christmas! Wilhelm Am 23.12.2013 19:38, schrieb Donald Carr: > Hola, > > I smell stale prl files: check /usr/lib, > Grep through the prls for the legacy library. >

Re: [Development] Qt 5.2.0 compilation fails on ArchLinux [SOLVED]

2013-12-24 Thread Wilhelm Meier
Hi, finally I solved this issue: ArchLinux defaults to Python3! Setting up a Python2 virtual environment solved the errors! Merry Christmas! Wilhelm Am 23.12.2013 19:38, schrieb Donald Carr: > Hola, > > I smell stale prl files: check /usr/lib, > Grep through the prls for the legacy library. >

Re: [Development] Qt 5.2.0 compilation fails on ArchLinux [SOLVED]

2013-12-24 Thread Wilhelm
Hi, finally I solved this issue: ArchLinux defaults to Python3! Setting up a Python2 virtual environment solved the errors! Merry Christmas! Wilhelm Am 23.12.2013 19:38, schrieb Donald Carr: > Hola, > > I smell stale prl files: check /usr/lib, > Grep through the prls for the legacy library. >

Re: [Development] Proposal for allowing handling of HTTP redirects in QNAM

2013-12-24 Thread Mandeep Sandhu
>> 2. New "redirected(QUrl)" signal to be emitted in case auto-redirects >> are enabled and a redirection occurs. > > This interface wouldn't be enough to let you distinguish between the > different types of redirect, though tbh I'm not sure that matters. By different types, I guess you mean the d

Re: [Development] Proposal for allowing handling of HTTP redirects in QNAM

2013-12-24 Thread Richard Moore
On 24 December 2013 07:57, Mandeep Sandhu wrote: > Hi All, > > Few days back I stumbled upon this task: > https://bugreports.qt-project.org/browse/QTBUG-8232 > > "QNetworkAccessManager should support redirection" > > I think this is a useful feature that can be added to QNAM as it makes > the life