From 0fd6bc31ee9f2b9fe7d1bff40542ef8e51d1adac Mon Sep 17 00:00:00 2001 From: Matthew Woehlke Date: Tue, 17 Feb 2015 13:45:22 -0500 Subject: Process global enums in declaration order In the same vein as the previous commit, process global enums in order added (which presumably is declaration order). For what we're doing at this point, this may not be as critical, but again is needed to avoid a spurious test failure. Change-Id: If32a07fee2e7e9b7699e01eda3408ed57855e947 Reviewed-by: John Cummings --- ApiExtractor/abstractmetabuilder.cpp | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) (limited to 'ApiExtractor/abstractmetabuilder.cpp') diff --git a/ApiExtractor/abstractmetabuilder.cpp b/ApiExtractor/abstractmetabuilder.cpp index 564f6c3ec..ebb3134ec 100644 --- a/ApiExtractor/abstractmetabuilder.cpp +++ b/ApiExtractor/abstractmetabuilder.cpp @@ -414,9 +414,8 @@ bool AbstractMetaBuilder::build(QIODevice* input) ReportHandler::flush(); // We need to know all global enums - QHash enumMap = m_dom->enumMap(); - ReportHandler::setProgressReference(enumMap); - foreach (EnumModelItem item, enumMap) { + ReportHandler::setProgressReference(m_dom->enumMap()); + foreach (EnumModelItem item, m_dom->enums()) { ReportHandler::progress("Generating enum model..."); AbstractMetaEnum *metaEnum = traverseEnum(item, 0, QSet()); if (metaEnum) { -- cgit v1.2.3