Difference: 0LASubrTextParseLine (6 vs. 7)

Revision 72018-05-07 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="APPXRuntimeSubroutineAPI"

.TEXT PARSE LINE

Line: 31 to 31
  - All processing has been moved to the APPX engine for faster performance
Changed:
<
<
- The --- PARSED file is returned containing one record for each column. If your application references the --- .TEXT PARSE RESULT field, it will also be populated subject to the restrictions above. The --- PARSED file does not have the same limitations.
>
>
- A file called --- PARSED is returned containing one record for each column. There are no size or number of columns limitations when results are returned in this file. If your application references the --- .TEXT PARSE RESULT field, it will also be populated subject to the restrictions above.
  - Fields surrounded by quotes will have the quotes removed (unless they are embedded in the the field).
Added:
>
>
- Delimiters enclosed in quotes will not act as a delimiter, ie, "Jacksonville, Florida" will be returned as one field (assuming a comma delimiter).
 - A backslash acts as an escape character to negate the following special character. For example:
  • C:\\Test will return C:\test
  • "embdded \" quote" will return 'embedded " quote'
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback