forked from qt-creator/qt-creator
Don't put QString in static attributes
It crashed in some places on our code-base due to the so-called "static initialization order fiasco". As a solution, it turns the variable into a function. This shouldn't have a penalty due to QStringLiteral. Change-Id: I9f8a955afdff878dc2f0db16fec861d81250c243 Reviewed-by: Tobias Hunger <tobias.hunger@theqtcompany.com>
This commit is contained in:
committed by
Aleix Pol Gonzalez
parent
954cabdde8
commit
b899684a89
@@ -131,10 +131,10 @@ bool operator <(const ImportKey &i1, const ImportKey &i2);
|
||||
class QMLJS_EXPORT Export
|
||||
{
|
||||
public:
|
||||
static const QString LibraryTypeName;
|
||||
static QString libraryTypeName();
|
||||
Export();
|
||||
Export(ImportKey exportName, QString pathRequired, bool intrinsic = false,
|
||||
const QString &typeName = LibraryTypeName);
|
||||
const QString &typeName = libraryTypeName());
|
||||
ImportKey exportName;
|
||||
QString pathRequired;
|
||||
QString typeName;
|
||||
@@ -211,9 +211,9 @@ public:
|
||||
void removeCoreImport(const QString &importId);
|
||||
|
||||
void addExport(const QString &importId, const ImportKey &importKey,
|
||||
const QString &requiredPath, const QString &typeName = Export::LibraryTypeName);
|
||||
const QString &requiredPath, const QString &typeName = Export::libraryTypeName());
|
||||
void removeExport(const QString &importId, const ImportKey &importKey,
|
||||
const QString &requiredPath, const QString &typeName = Export::LibraryTypeName);
|
||||
const QString &requiredPath, const QString &typeName = Export::libraryTypeName());
|
||||
|
||||
void iterateOnCoreImports(const ViewerContext &vContext,
|
||||
std::function<bool(const CoreImport &)> const &iterF) const;
|
||||
|
||||
Reference in New Issue
Block a user