Post by Robert on Nov 23, 2023 13:32:47 GMT -5
George,
Right now, there are no SPF-supplied functions to do EBCDIC translation, and thinBasic has none either. This suggestion describes a possible implementation.
Current thinBasic translation functions are named like,
object-str = SourceToObject$(source-str)
For instance,
UTF8_str = AnsiToUtf8$(ansi_str)
But, SPFLite function names that return strings have names that begin with Get. So, to be SPFLite-consistent instead of thinBasic consistent, we need to follow that naming pattern.
Here are the proposed functions:
ebcdic-str = Get_EBCDIC_from_ANSI$ (ansi-str)
ansi-str = GET_ANSI_from_EBCDIC$ (ebcdic-str)
Description:
SPFLite maintains internal translation tables, based on its reading of the EBCDIC.SOURCE translation file. Those internal tables would be used to perform the translation in these new functions.
It is not an error if the supplied string value is null (""); it would simply return a null "" string back.
R
Right now, there are no SPF-supplied functions to do EBCDIC translation, and thinBasic has none either. This suggestion describes a possible implementation.
Current thinBasic translation functions are named like,
object-str = SourceToObject$(source-str)
For instance,
UTF8_str = AnsiToUtf8$(ansi_str)
But, SPFLite function names that return strings have names that begin with Get. So, to be SPFLite-consistent instead of thinBasic consistent, we need to follow that naming pattern.
Here are the proposed functions:
ebcdic-str = Get_EBCDIC_from_ANSI$ (ansi-str)
ansi-str = GET_ANSI_from_EBCDIC$ (ebcdic-str)
Description:
SPFLite maintains internal translation tables, based on its reading of the EBCDIC.SOURCE translation file. Those internal tables would be used to perform the translation in these new functions.
It is not an error if the supplied string value is null (""); it would simply return a null "" string back.
R
