Clarify array type checking, no out-of-bounds analysis
This commit is contained in:
parent
e21a7c323b
commit
18c724071d
@ -358,8 +358,8 @@ As the parser only does syntactic checking, additional semantic checks are imple
|
|||||||
- Checking that all execution paths of a non-void function return a value
|
- Checking that all execution paths of a non-void function return a value
|
||||||
- You may assume that there is no dead code
|
- You may assume that there is no dead code
|
||||||
- Type checking (remember, neither implicit nor explicit type conversions)
|
- Type checking (remember, neither implicit nor explicit type conversions)
|
||||||
- Includes checking operations on arrays (including array size)
|
|
||||||
- Includes checking arguments and return types for call expressions
|
- Includes checking arguments and return types for call expressions
|
||||||
|
- Don't forget that an array's type includes its size
|
||||||
|
|
||||||
Semantic checking may stop on the first error encountered.
|
Semantic checking may stop on the first error encountered.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user