BCX Documentation Version 8.3.1, November 26, 2025

[Robert]

BCX Documentation Version 8.3.1, November 26, 2025

REVISIONS

Code Select Expand


Robert Wishlaw
 ... changed the Return Value: Data Type: of the ANSITOWIDE$ function from LPOLESTR to PWSTR. Added NULLTerm [OPTIONAL] parameter description.

 ... changed the UnicodeStr parameter Data Type: of the WIDETOANSI$ function from LPOLESTR to LPWSTR.

 ... replaced the WIDETOANSI$ function example.

 ... added ANSITOWIDE$ function example.

 ... corrected several errors in the descriptions in the GETSAVEASFILENAME$ function section.

 ... replaced, where appropriate, the acronym "ASCII" with "Windows Code Page code point".
     The replacement usually was made where a reference existed that included the numeric 128 to 255
     code point values used in Windows code pages. "ASCII" was retained in cases where the reference
     was made to ASCII code points (0 - 127), common to all Windows Code Pages.
     "ANSI", the acronym for the American National Standards Institute, was considered as a replacement
     for the inappropriate "ASCII" usage, but was rejected as a misnomer.
     In a Glossary of terms published by Microsoft, it is stated,
     "The term "ANSI" as used to signify Windows code pages is a historical reference,
     but is nowadays a misnomer that continues to persist in the Windows community.
     The source of this comes from the fact that the Windows code page 1252 was originally based on an ANSI draft,
     which became International Organization for Standardization (ISO) Standard 8859-1."

 ... repaired hundreds of broken hyperlinks to their primary reference document.


SHA-256

Code Select Expand

1738CC30076017A3AA1278B271C2B004395151251A5E412E0552FB563A391DF1