Difference: APPX610UpgradeInstallation (21 vs. 22)

Revision 222021-07-20 - MisaghKarimi

Line: 1 to 1
 
META TOPICPARENT name="Main.Appx600Installation"

APPX 6.1 Upgrade Instructions

Line: 143 to 143
  1. All --- TEMP fields are now Unicode fields. If you are using --- TEMP to interface with external programs or O/S level subroutines, this may have an impact if they not expecting to receive UTF-32 encoded data. Also, CNV BIN on a --- TEMP 2 or ---TEMP 4 no longer works since those fields are larger than 4 bytes in size (in this case APPX will give you compilation error during Em build). A number of --- WORK RAW xx fields have been added - you can use these in place of --- TEMP fields if you need a non Unicode field.
Changed:
<
<		2. Older subroutines in 0LA have various issues:
>
>		2. --- STREAM BUFFER field is also converted to Unicode. STREAM functions are reading and writing data in utf8 encoding unless the mode is specified as binary.

3. Older subroutines in 0LA have various issues:

 
  • FIND STRING LENGTH - limited to strings of 32k
  • INSERT STRING - limited to strings of 32k
  • REMOVE STRING - limited to strings of 32k
You should use the newer .TEXT routines for string functions.
Changed:
<
<		3. Any direct CALL statements to engine ,RT functions will have to be reviewed and possibly changed.
>
>		4. Any direct CALL statements to engine ,RT functions will have to be reviewed and possibly changed.
 
Changed:
<
<		4. A group field containing a Unicode field can only be moved to or from another group field. A Unicode field cannot be moved to or from a Group. This is detected at compile time so you can batch compile your applications to find these errors.
>
>		5. A group field containing a Unicode field can only be moved to or from another group field. A Unicode field cannot be moved to or from a Group. This is detected at compile time so you can batch compile your applications to find these errors.
 
Changed:
<
<		5. APPX now uses a LF character (ASCII 10) instead of a ¶ (ASCII 182) as a line feed character in text fields. Existing text data will display the ¶ character instead of a new line. To correct this, you need to search any text fields for a ¶ and replace it with a LF character. If you were already using APPX_END_PARAGRAPH to set the line feed to 0x10, this is no longer necessary as your data is already using a LF.
>
>		6. APPX now uses a LF character (ASCII 10) instead of a ¶ (ASCII 182) as a line feed character in text fields. Existing text data will display the ¶ character instead of a new line. To correct this, you need to search any text fields for a ¶ and replace it with a LF character. If you were already using APPX_END_PARAGRAPH to set the line feed to 0x10, this is no longer necessary as your data is already using a LF.
 
Changed:
<
<		6. Field Type of fields that are storing pointer values have been changed from Numeric (binary) to ALPHA(8). Most of these fields are used internally and you shouldn't worry about them if you have not used them in your application. Here are the list of pointer fields in APPX:
>
>		7. Field Type of fields that are storing pointer values have been changed from Numeric (binary) to ALPHA(8). Most of these fields are used internally and you shouldn't worry about them if you have not used them in your application. Here are the list of pointer fields in APPX:
 
  • 0AD IMGEDIT INT ADDR
  • 0AD SEGEN SE POINTER
Line: 178 to 180
 
  • 0LA STACK PCB POINTER
  • 0LA STREAM FILE POINTER
  • 0LA STREAMS FILE POINTER
Changed:
<
<		7. 0LA RETURN CODE is still a 4 byte binary field. So, you cannot expect to receive an 8 byte pointer (in 64-bit release) in the return code field.
>
>		8. 0LA RETURN CODE is still a 4 byte binary field. So, you cannot expect to receive an 8 byte pointer (in 64-bit release) in the return code field.
 
Changed:
<
<		8. Regular Expression library has changed to support Unicode characters. The new library doesn't like blank or unescaped patterns. You will get a run-time error if it doesn't like the pattern.
>
>		9. Regular Expression library has changed to support Unicode characters. The new library doesn't like blank or unescaped patterns. You will get a run-time error if it doesn't like the pattern.
 
Changed:
<
<		9. As the result of the fix for bugs #799, #2498, and #4792, the way APPX finds a subroutine called by a GOSUB statement has changed. If you received "Duplicate Label" or "Could Not Compile GOSUB" error during em creation, it is because you called a subroutine without specifying an application id or called an internal subroutine (a subroutine within another subroutine) with an application id. We recommend making changes to your application to fix these errors, however, you can set APPX_USE_PRE_61_GOSUB environment variable to revert back to old behavior.
>
>		10. As the result of the fix for bugs #799, #2498, and #4792, the way APPX finds a subroutine called by a GOSUB statement has changed. If you received "Duplicate Label" or "Could Not Compile GOSUB" error during em creation, it is because you called a subroutine without specifying an application id or called an internal subroutine (a subroutine within another subroutine) with an application id. We recommend making changes to your application to fix these errors, however, you can set APPX_USE_PRE_61_GOSUB environment variable to revert back to old behavior.
 

Comments:

Read what other users have said about this page or add your own comments.

View topic | History: r34 < r33 < r32 < r31 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback