Oswald Buddenhagen 849f1f9efd don't allow overloading of built-in functions ... the functions are not versioned or scoped, so user-defined overloads would mess up qmake's own feature files. it seems safer to break user projects than to allow the user to break qmake. Change-Id: I020a2e6416bbb6e2fd2ece339629d848c00c8398 Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com> Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>		2012-09-18 07:47:14 +02:00
..
ioutils.cpp	port qmake to qt creator's qmake language evaluator	2012-09-11 00:13:01 +02:00
ioutils.h	port qmake to qt creator's qmake language evaluator	2012-09-11 00:13:01 +02:00
proitems.cpp	port qmake to qt creator's qmake language evaluator	2012-09-11 00:13:01 +02:00
proitems.h	don't pretend that break()/next()/return() are functions	2012-09-13 03:42:44 +02:00
qmake_global.h	introduce qmake variable abstractions	2012-09-07 15:39:31 +02:00
qmakebuiltins.cpp	don't allow overloading of built-in functions	2012-09-18 07:47:14 +02:00
qmakeevaluator.cpp	don't allow overloading of built-in functions	2012-09-18 07:47:14 +02:00
qmakeevaluator.h	don't allow overloading of built-in functions	2012-09-18 07:47:14 +02:00
qmakeevaluator_p.h	port qmake to qt creator's qmake language evaluator	2012-09-11 00:13:01 +02:00
qmakeglobals.cpp	port qmake to qt creator's qmake language evaluator	2012-09-11 00:13:01 +02:00
qmakeglobals.h	port qmake to qt creator's qmake language evaluator	2012-09-11 00:13:01 +02:00
qmakeparser.cpp	remove the entirely insane whitespace compression	2012-09-18 07:47:05 +02:00
qmakeparser.h	don't pretend that break()/next()/return() are functions	2012-09-13 03:42:44 +02:00