Bug #5399
schema parsing failure when a string literal ends in a tilde
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
History
#1 Updated by Greg Shah about 3 years ago
In a .df, if a field definition has a string literal that has a tilde as its last character, in the 4GL this is handled as a valid string but in FWD the ending " character will be consumed as an escaped value and the string will not properly end. This breaks the proper parsing of the schema.
Example: HELP "Some text here that ends in a tilde ~".
A customer provided a .df which works in the 4GL and has this construct. They used this on Windows. We need to confirm this will also work on Linux/UNIX. My theory is that in schema parsing, the end of line terminates the string implicitly unless the end of line itself is escaped.