Difference between revisions of "Migration to Unicode"

m (Added a first version)
 
m (→‎Temporary solution: Splitted item #4.)
Line 46: Line 46:
 
| <e>EXECUTION_ENVIRONMENT_32</e>
 
| <e>EXECUTION_ENVIRONMENT_32</e>
 
|}
 
|}
−
# Consider using <e>READABLE_STRING_32</e> for argument types.
+
# 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>.
 
# Consider using <e>SHARED_EXECUTION_ENVIRONMENT</e> to access <e>EXECUTION_ENVIRONMENT_32</e>.
−
# If you cannot immediately change argument types to take <e>READABLE_STRING_32</e>, use <e>READABLE_STRING_GENERAL</e>. If you want to operate on files with an unknown string type for their names (i.e. <e>READABLE_STRING_GENERAL</e>), use <e>FILE_UTILITIES</e>. This is an expanded class and can be used as described for <e>UTF_CONVERTER</e>.
+
# If you want to operate on files with an unknown string type for their names (i.e. <e>READABLE_STRING_GENERAL</e>), use <e>FILE_UTILITIES</e>. This is an expanded class and can be used as described for <e>UTF_CONVERTER</e>.

Revision as of 09:48, 26 September 2012


This is a summary of the recommendations for adapting applications to handle Unicode.

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.

Temporary solution

  1. Replace types using the following table:
Old class New class
STRING_8 STRING_32
FILE_NAME FILE_NAME_32
DIRECTORY_NAME DIRECTORY_NAME_32
FILE FILE_32
RAW_FILE RAW_FILE_32
PLAIN_TEXT_FILE PLAIN_TEXT_FILE_32
DIRECTORY DIRECTORY_32
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.
  3. Consider using SHARED_EXECUTION_ENVIRONMENT to access EXECUTION_ENVIRONMENT_32.
  4. If you want to operate on files with an unknown string type for their names (i.e. READABLE_STRING_GENERAL), use FILE_UTILITIES. This is an expanded class and can be used as described for UTF_CONVERTER.
Retrieved from "https://dev.eiffel.com/index.php?title=Migration_to_Unicode&oldid=14550"