6 Commits

Author	SHA1	Message	Date
Rintaro Ishizaki	bd3b2c6601	[Parse] Add warning for compound name in compilation condition in swift3	2017-03-29 00:43:28 +09:00
Rintaro Ishizaki	3943b8a77c	[Parse] Add warning with fix-it for combination of '||' and '&&' in ... compilation condition in Swift3 mode.	2017-03-24 18:28:23 +09:00
Rintaro Ishizaki	b56ab17fa5	[Parse] Separate compilation condition validation and evaluation ... Fixes: https://bugs.swift.org/browse/SR-3455 https://bugs.swift.org/browse/SR-3663 https://bugs.swift.org/browse/SR-4032 https://bugs.swift.org/browse/SR-4031 Now, compilation conditions are validated at first, then evaluated. Also, in non-Swift3 mode, '&&' now has higher precedence than '||'. 'A || B && C || D' are evaluated as 'A || (B && C) || D'. Swift3 source breaking changes: * [SR-3663] This used to be accepted and evaluate to 'true' because of short circuit without any validation. #if true || true * 12 = try Anything is OK? print("foo") #endif In this change, remaining expressions are properly validated and diagnosed if it's invalid. * [SR-4031] Compound name references are now diagnosed as errors. e.g. `#if os(foo:bar:)(macOS)` or `#if FLAG(x:y:)` Swift3 compatibility: * [SR-3663] The precedence of '||' and '&&' are still the same and the following code evaluates to 'true'. #if false || true && false print("foo") #endif	2017-03-23 01:25:29 +09:00
Rintaro Ishizaki	d23c256155	[test] Add several test cases for #if condition. ... https://bugs.swift.org/browse/SR-3663 https://bugs.swift.org/browse/SR-4032 https://bugs.swift.org/browse/SR-4031	2017-03-23 01:25:29 +09:00
Rintaro Ishizaki	b2d549e0c1	[Parse][Swift3] Add a warning for unsupported conditional compiliation expression	2017-01-18 05:25:14 +09:00
Rintaro Ishizaki	b950f06f3e	[Parse] Disallow unsupported condition expression in #if directive ... In non-Swift3 mode. Previously: #if FOO = false #elseif FOO ? false : true #endif were silently accepted. i.e. '= false' and '? false : true' were silently ignored.	2017-01-17 22:11:11 +09:00