| |
| META TOPICPARENT |
name="UnicodeTestPlan" |
Unicode ILF Literals |
| |
- If the field type of the other operand is Unicode or National the literal will compile to a UTF-32 literal.
- If the field type of the other operand is Raw the literal will be compiled to a RAW literal.
Test Plan: |
|
<
< | Encoding Types: (untested) |
>
> | Encoding Types: |
| |
Test Requirements: |
|
<
< | Are unicode literals interpreted as characters when the left operand is a RAW alpha?
Are unicode literals treated correctly when the left operand is UNICODE and NATIONAL? |
>
> |
- Are unicode literals interpreted as characters when the left operand is a RAW alpha?
- Are unicode literals treated correctly when the left operand is UNICODE and NATIONAL?
|
| | BUGS |
|
<
< |
- Entering invalid literals causes process not to run (first attempt) or Appx to crash (second attempt). Invalid literal examples: \U with less than 8 hex digits, or \u with non hex digits.
|
| | \ No newline at end of file |
|
>
> |
- Entering invalid literals causes process not to run (first attempt) or Appx to crash (second attempt). Invalid literal examples: \U with less than 8 hex digits, or \u with non hex digits. * FIXED * April 5 engine. Invalid literals create compile time errors.
|
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.