Difference between revisions of "Migration to Unicode"

m (Fixed a typo.)
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
 
[[Category:Unicode]]
 
[[Category:Unicode]]
  
−
This is a summary of the recommendations for adapting applications to handle Unicode.
+
This is a summary of the recommendations for adapting applications to handle Unicode. Although some recommendations can be applied in earlier version of EiffelStudio starting from 5.6, the following recommendations are made for 7.2 and higher.
  
 
====General rule====
 
====General rule====
Line 38: Line 38:
 
# Consider using <e>READABLE_STRING_32</e> for argument types. If you cannot immediately change argument types to take <e>READABLE_STRING_32</e>, e.g. because this is a library class, use <e>READABLE_STRING_GENERAL</e> and perform all the necessary conversions inside the routine.
 
# Consider using <e>READABLE_STRING_32</e> for argument types. If you cannot immediately change argument types to take <e>READABLE_STRING_32</e>, e.g. because this is a library class, use <e>READABLE_STRING_GENERAL</e> and perform all the necessary conversions inside the routine.
 
# If you need to convert one UTF encoding into another one, use <e>UTF_CONVERTER</e>. This is an expanded class, so it's possible to declare a local variable of this type and call features on it without explicit object creation.
 
# If you need to convert one UTF encoding into another one, use <e>UTF_CONVERTER</e>. This is an expanded class, so it's possible to declare a local variable of this type and call features on it without explicit object creation.
−
# Consider using <e>SHARED_EXECUTION_ENVIRONMENT</e> to access <e>EXECUTION_ENVIRONMENT_32</e>.
 

Latest revision as of 14:30, 15 February 2013


This is a summary of the recommendations for adapting applications to handle Unicode. Although some recommendations can be applied in earlier version of EiffelStudio starting from 5.6, the following recommendations are made for 7.2 and higher.

General rule

  1. Never use STRING_8 or any variant of it unless you write a program that is going to be deleted in 5 minutes after running it. Do not even consider using STRING_8 or its variant. Always use IMMUTABLE_STRING_32, READABLE_STRING_32 or STRING_32.
  2. Do not use classes from third-party libraries that take STRING_8 rather than STRING_32.
  3. Use PATH to manipulate file or directory names
  4. Whenever an API takes a READABLE_STRING_GENERAL argument, assume that STRING_8 will be treated as Unicode strings in the range 0 .. 255, unless explicitly noted.

Temporary solution

  1. Replace types using the following table:
Old class New class
STRING_8 STRING_32
FILE_NAME PATH
DIRECTORY_NAME PATH
KL_BINARY_INPUT_FILE KL_BINARY_INPUT_FILE_32
KL_TEXT_OUTPUT_FILE KL_TEXT_OUTPUT_FILE_32
EXECUTION_ENVIRONMENT EXECUTION_ENVIRONMENT_32
  1. Consider using READABLE_STRING_32 for argument types. If you cannot immediately change argument types to take READABLE_STRING_32, e.g. because this is a library class, use READABLE_STRING_GENERAL and perform all the necessary conversions inside the routine.
  2. If you need to convert one UTF encoding into another one, use UTF_CONVERTER. This is an expanded class, so it's possible to declare a local variable of this type and call features on it without explicit object creation.
Retrieved from "https://dev.eiffel.com/index.php?title=Migration_to_Unicode&oldid=14653"