Change-Id: I2cc1236552e00e99a846b0d4b724135724f175fc
Task-number: QTCREATORBUG-3666
Reviewed-on: http://codereview.qt.nokia.com/4241


Reviewed-by: Leandro T. C. Melo <leandro.melo@nokia.com>

The distinction between QmlJS and QmlJS::Interpreter has always been
weak and the extra namespace just added an unnecessary complication.

Change-Id: I4db8ef4bd91b5f6bf610a9d23fdbf55bd60250fc
Reviewed-on: http://codereview.qt.nokia.com/2743


Reviewed-by: Fawzi Mohamed <fawzi.mohamed@nokia.com>

Previously Context was not entirely thread safe and had to be
copied locally. Now it is thread safe and its lifetime
managed by QSharedPointer.

The non-safe parts were moved into ScopeChain in a previous commit.

Change-Id: I851a93de85cbd6391dbea0fe33b011e2e093addb
Reviewed-on: http://codereview.qt.nokia.com/1695


Reviewed-by: Fawzi Mohamed <fawzi.mohamed@nokia.com>

Context is created by Link and has information about imports
for all Documents in a Snapshot.

ScopeChain represents how lookup is done at a specific place in
a Document.

Change-Id: I874102d57bbaf1a497fa3f27633bed6ee75dcf10
Reviewed-on: http://codereview.qt.nokia.com/1694


Reviewed-by: Fawzi Mohamed <fawzi.mohamed@nokia.com>

Change-Id: I91331b7039e27e2f57cc19b985c8ed86c955ec9e
Reviewed-on: http://codereview.qt.nokia.com/1042


Reviewed-by: Fawzi Mohamed <fawzi.mohamed@nokia.com>

Change-Id: Iaeb96ff67cfc92bcddeb1b7075b7fdcbaed317c0
Reviewed-on: http://codereview.qt.nokia.com/691


Reviewed-by: Thomas Hartmann <Thomas.Hartmann@nokia.com>

Task-number: QTCREATORBUG-3541
Change-Id: Ida8e59b65836c8515fbfbd2a9e4737d9ae04e76c
Reviewed-on: http://codereview.qt.nokia.com/639


Reviewed-by: Fawzi Mohamed <fawzi.mohamed@nokia.com>

correctly insert the scope for code blocks in UiScriptBindings and
UiPublicMember, and improve find usages for types (correctly detecting
variables in the same scope)

Change-Id: Iaaf1a59f041f3831fbe04243b220fb85fde76479
Reviewed-on: http://codereview.qt.nokia.com/335


Reviewed-by: Christian Kamm <christian.d.kamm@nokia.com>

To avoid lots of follow-up errors where the root cause is a failed
prototype resolution or a prototype cycle.

Task-number: QTCREATORBUG-4952
Change-Id: Id474c8c6c152c993aca8c6c421b6d88eb1481676
Reviewed-on: http://codereview.qt.nokia.com/36


Reviewed-by: Thomas Hartmann <Thomas.Hartmann@nokia.com>

UiPublicMember is now initialized with a statement.

Change-Id: I8b73d583be1ee7183f4074bce49d5390e38631a2

To avoid order-of-initialization problems.

Reviewed-by: Thomas Hartmann

Task-number: QTCREATORBUG-2306

Reviewed-by: Roberto Raggi

Unifying the api and exposing the options.

Missing files should be a warning.

The problem was that several lookup calls suddenly failed because
the actual QML types were no longer in the default scope chain. However,
the QML documentation says the type names are in the scope.

Also, 'MyComponent.' in a JS-expression context only showed the attached
properties of MyComponent and missed the enums.

With this change completion now may offers too many options, but that's
better than missing some.

This reverts parts of 490f2797

Reviewed-by: Leandro Melo

Reviewed-by: hjk

Each Components starts a new scope for ids. Using a stack to check
this properly.

We are checking for duplicate ids and duplicate property definitions now.

Reviewed-by: Erik Verbruggen

Also
* check the condition of the 'for(var' statement for assignment
* allow comma expressions in 'for(var'

Reviewed-by: Erik Verbruggen

Reviewed-by: Roberto Raggi

Reviewed-by: Roberto Raggi

Reviewed-by: Roberto Raggi

The "value might be 'undefined'" warning triggered whenever the static
expression evaluator failed to produce a value. At the moment, it does
so for almost all non-trivial expressions.

The warning is now disabled.

Task-number: QTCREATORBUG-3208

Task-number: QTCREATORBUG-3071
Reviewed-by: Erik Verbruggen

It still generates too many false-negatives for now. Will be enabled
once the remaining lookup failures have been fixed.

Reviewed-by: Erik Verbruggen

Reviewed-by: Erik Verbruggen

Link now caches imports. That means importing the same library (say, Qt)
from more than one file no longer creates an importing namespace for
each one. Instead, a single one is created for the instance of Link.

To make this work, the type environment in ScopeChain has been given its
own type: Interpreter::TypeEnvironment. That has the added benefit of
being able to carry meta-information about imports. You can use
TypeEnvironment::importInfo(qmlComponentName) to get information about
the import node that caused the import of the component.

Reviewed-by: Roberto Raggi

* If possible, create LookupContexts through SemanticInfo; it caches the
  linked Context and will be faster.
* Contexts now own their Engine.

Reviewed-by: Lasse Holmstedt