GitLab

instead of being os-agnostic, interpret the os-native expansion style,
so it is consistent with proper (shell) command lines.

don't interpret quotes, as this function is meant for expanding isolated
filepaths, where nobody would expect quoting. instead, use the windows
style of simply not doing an expansion if a referenced variable is not
found, which should be good enough - it's rather unlikely that something
which happens to be an expansion of an existing variable is actually not
meant to be one.

(Instead of the initial system environment.)

Reviewed-by: kh1

(In QtCreator the wizard would take care of that.)

To keep the breakpoint state machinery simple

Task-number: QTCREATORBUG-3084

Task-number: QTCREATORBUG-2924
Reviewed-by: ck

Task-number: QTCREATORBUG-3090
Reviewed-by: ck

A full evaluate() call resolves the property and continues to the
underlying type. If we use Evaluate::reference() instead, we only the
first step is done and we can get at the source location if a
ASTPropertyReference is returned.

Reviewed-by: Erik Verbruggen

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

Reviewed-by: Erik Verbruggen

Reviewed-by: con

Reviewed-by: hjk
Task-number: QTCREATORBUG-3099

Task-number: QTBUG-15170

Clear controls that are not applicable to type, but save
and restore their value once the type is again choosen.

Remove BreakHandler::hasPendingBreakpoints, handle new types
in CDB and gdb. Start fixing Breakpoint-Dialog.
Add assignment of Breakpointresponse from BreakpointParameters.

Reviewed-by: hjk