| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Reviewed-by: Volker Hilsheimer
|
| |
|
|
|
|
| |
It tries to keep the semantics of QString::append(QByteArray) as much as possible.
|
|
|
|
| |
make compiler distinguishing both happy.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QSharedPointer"
This reverts commit fb51a10ee0451274a430227566ae26efb2ac4474.
Sorry, it didn't work. I can fix the MSVC error, but the problem is
that older GCC versions (4.2) fail with the following code:
template<typename T> struct Buffer
{
char buffer[128] __attribute__((aligned(__alignof__(T))));
};
The same works fine in GCC 4.4.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
are declared in this file.
The one-definition rule allows the forward declaration appearing below to
apply to code that was earlier. Therefore, if the compiler finds out
how to delete the object, we can allow a QSharedPointer of a forward-
declared-type.
This means the actual problem is just a warning with g++. To catch the
error, we need a separate .cpp file and I'd rather run this as an
external test.
|
|
|
|
|
|
|
|
|
| |
one go.
This avoids one memory allocation. Currently, we only support calling
the default constructors. I will *NOT* implement argument passing for
C++03. I will implement it with rvalue references for C++0x-capable
compilers.
|
|
|
|
|
|
|
|
|
| |
This obviously only works for classes that derive from QObject. And
you must remember that QSharedPointer controls the QObject's lifetime,
not the QObject parent-child relationship.
Reviewed-by: dt
Reviewed-by: Bradley T. Hughes
|
|\ |
|
| |
| |
| |
| | |
Reviewed-by: trustme
|
| |
| |
| |
| |
| |
| |
| | |
This is related to the following fix:
70137e0601549af1056082cdfbb4f141c70befab
Reviewed-by: trustme
|
| |
| |
| |
| |
| |
| |
| | |
Directly put a QRingBuffer from one QRingBuffer to
another QRingBuffer.
Reviewed-by: Thiago Macieira
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
support
Also: QString::fromUtf16() -> QString::fromWCharArray()
WCHAR & TCHAR -> wchar_t
LPTSTR/LPCTSTR -> LPWSTR/LPCWSTR
Documentation update
Merge-request: 604
Reviewed-by: Marius Storm-Olsen <marius@trolltech.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
In QTime::currentTime(), the pointer to the tm structure was used
without being initialized.
Task-number: 256889
Reviewed-by: Markus Goetz
|
| |
| |
| |
| |
| | |
These four enum values are used in variables of type Section, but aren't in it.
With gcc 4.4, it displays a warning that the value is lower than the lowest value
|
| |
| |
| |
| |
| |
| |
| | |
There's no need to have separate cast-checker functions, plus the cast-
and centralise the function to create the object.
Reviewed-by: TrustMe
|
|\ \
| |/
| |
| |
| |
| | |
Conflicts:
src/plugins/gfxdrivers/directfb/qdirectfbpaintengine.cpp
src/plugins/gfxdrivers/directfb/qdirectfbpixmap.cpp
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
enabled.
This allows mixing of debug and non-debug code (possible on Unix
systems) without causing assertion failures.
Reviewed-by: Bradley T. Hughes <bradley.hughes@nokia.com>
|
|\ \
| |/
| |
| |
| | |
Conflicts:
tests/auto/qsqldatabase/tst_databases.h
|
| |
| |
| |
| |
| |
| |
| | |
Two strings are only equal if they have the same size.
Task-number: 256763
Reviewed-by: TrustMe
|
| |
| |
| |
| |
| |
| | |
Removed lots of places where we check for Tiger. Now we can assume it.
Reviewed-by: Morten Sørvig
|
|\ \
| |/
| |
| |
| |
| |
| |
| | |
Conflicts:
src/3rdparty/webkit/VERSION
src/3rdparty/webkit/WebCore/ChangeLog
src/3rdparty/webkit/WebKit/qt/ChangeLog
tests/auto/qgraphicsitem/tst_qgraphicsitem.cpp
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In 4.4 QRectF handled flat rectangles in the same fashion as QRect does,
but that changed with Lars' and Jo's optmizations done in the falcon
branch. The difference is that the optimized version only checks whether
the width or height is 0, whereas in 4.4 both had to be 0 (isNull()) before
we bailed out.
This regression also introduced a regression in
QGraphicsItem::childrenBoundingRect().
Auto-test included.
Task-number: 254995
Reviewed-by: Lars
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
enum Qt::Uninitialized contains one value, which is also called
Uninitialized. Because the type and the value used the same name,
wherever the type Qt::Uninitialized was used in a function signature,
you had to include the enum keyword. But qdoc's preprocessor doesn't
like that, so you have to take the enum keyword out of the signatures.
But then the compiler complains because the type and the value look
the same. So I had to change the enum type name to Initialization, so
the compiler can distinguish it from the value name. And qdoc likes
that too.
|
| |
| |
| |
| |
| |
| |
| | |
Directly construct uninitialized QByteArrays of required size
instead of default-constructing one and resizing it afterwards.
Reviewed-by: mariusSO
|
| |
| |
| |
| |
| |
| |
| | |
Contrary to the QByteArray::QByteArray(int size, enum Qt::Uninitialized)
constructor this does not initialize its data.
Reviewed-by: mariusSO
|
| |
| |
| |
| | |
Reviewed-by: mariusSO
|
| |
| |
| |
| |
| |
| |
| | |
There is no BC issue as the changed constructor was introduced
recently and there is no released version of Qt using it.
Reviewed-by: mariusSO
|
| |
| |
| |
| |
| |
| |
| |
| | |
The QStringBuilder class documentation is marked \internal.
A section has been added to the documentation for QString
that explains how to use the reimplemented '%' operator of
QStringBuilder to obtain more efficient string concatenation
operations.
|
| |
| |
| |
| |
| |
| |
| |
| | |
All the qdoc errors are fixed in QStringBuilder, but because the
class is a template class and uses strange templates, qdoc gets
very confused, and the resulting documentation for QStringBuilder
is not complete and accurate. To fix this correctly will require
changes to the qdoc program.
|
| |
| |
| |
| | |
Reviewed-by: Trust Me
|
|\ \
| |/ |
|
| |
| |
| |
| | |
Reviewed-by: Trust Me
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Only release branches are allowed to have the Commercial usage header.
All other branches must have the No Commercial Usage header.
Reviewed-by: Trust Me
|
| | |
|
| |
| |
| |
| |
| |
| | |
That reduces memory usage.
Reviewed-by: denis
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Some checks where in the wrong locations, and some endifs where
hard to read.
Merge-request: 611
Reviewed-by: Marius Storm-Olsen <marius@trolltech.com>
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
So far, only operator% was working for concatenation in those circumnstances.
Now, defining QT_USE_FAST_OPERATOR_PLUS and QT_USE_FAST_CONCATENATION is
enough, so user code will work without any source changes.
Reviewed-by: joao
|
| |
| |
| |
| | |
Reviewed-by: TrustMe
|
| | |
|
| |
| |
| |
| | |
Reviewed-by: Trust Me
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
From a merge request #553 by Gordon Schumacher:
During a build internal to Qt, if a header included by qlocale.cpp
itself includes qlocale.h, then QLOCALE_CPP will never be set. If you
attempt to build qmake from its own .pro file, qmake_pch.h includes
qtextstream.h, which (now) includes qlocale.h, thus causing a compile
error trying to call the QSystemLocale(bool) function
Inspired-by: Gordon Schumacher <gordon@rebit.com>
|
|\ \ |
|
| | | |
|