uChar() (Char() for unicode)

Num3 · Post by **Num3** » Tue Jun 10, 2008 6:14 pm

Tip by Danilo on the IRC...

CompilerIf #PB_Compiler_Unicode
  Procedure.s uChr(char)
    char$ = " "
    PokeW(@char$, char & $FFFF)
    ProcedureReturn char$
  EndProcedure
  Macro Chr(x)
    uChr(x)
  EndMacro
CompilerEndIf

A$ = "test " + Chr($20AC) + " " + Chr($FB30)
Debug a$

Trond · Post by **Trond** » Tue Jun 10, 2008 6:34 pm

What's wrong with Chr()? It should work in unicode mode.

Num3 · Post by **Num3** » Tue Jun 10, 2008 6:44 pm

Trond wrote:What's wrong with Chr()? It should work in unicode mode.

Doesn't work...

Seems none of the string functions are working

Post by **Fred** » Tue Jun 10, 2008 7:00 pm

Then you have a big problem.. Your source has to be in utf8 format when using unicode constants.

Kaeru Gaman · Post by **Kaeru Gaman** » Tue Jun 10, 2008 7:18 pm

...when your source is in UTF-8 and Create Unicode Exe is on, Chr() works with 2byte....

or has this been changed again?

Num3 · Post by **Num3** » Tue Jun 10, 2008 7:25 pm

The manual says:

When developing a unicode program, it's recommended to set the IDE in UTF-8 mode, so all the source files will be unicode ready.

Maybe the statement should be rephrased

ts-soft · Post by **ts-soft** » Tue Jun 10, 2008 7:29 pm

I have my IDE default set to utf-8, why should i use ascii???

Num3 · Post by **Num3** » Tue Jun 10, 2008 7:37 pm

ts-soft wrote:I have my IDE default set to utf-8, why should i use ascii???

Because it's the default that comes with PB...
I think 90% of us didn't even bother to change that

Trond · Post by **Trond** » Tue Jun 10, 2008 7:44 pm

The string functions should work with unicode characters even when the source is set to ascii. You just have to generate those characters at run-time or read them from a file, as you obviously can't have unicode characters in an ascii file.

I'd vote for just dropping the ascii mode altogether, as UTF-8 is mostly backwards compatible with it, unless you use special characters, in which case you couldn't have used ascii anyways.

Num3 · Post by **Num3** » Tue Jun 10, 2008 7:51 pm

my favourite now:

+1

ts-soft · Post by **ts-soft** » Tue Jun 10, 2008 7:58 pm

ansi-mode, not ascii mode

but you are right, the ansi-mode is needless

Trond · Post by **Trond** » Wed Jun 11, 2008 10:14 am

ts-soft wrote:ansi-mode, not ascii mode

Are you sure? ANSI defines only the first 128 characters, while PB uses all 256 in plain text mode. How could that possibly be called an ANSI mode?

ts-soft · Post by **ts-soft** » Wed Jun 11, 2008 10:28 am

ASCII is orginal 7-Bit Code, ANSI is 8-Bit, but the official norm is:
ISO/IEC 8859
but i'm no 100% sure

Psychophanta · Post by **Psychophanta** » Wed Jun 11, 2008 10:50 pm

Nowadays, when someone says ASCII he is usually referring to Extended-ASCII.

By the way, just now i realize that a macro can have the same name as a internal function. I remember to do that in the past (i.e. using older PB versions) but it didn't work

dell_jockey · Post by **dell_jockey** » Thu Jun 12, 2008 7:25 am

Psychophanta wrote: By the way, just now i realize that a macro can have the same name as a internal function. I remember to do that in the past (i.e. using older PB versions) but it didn't work

Is this now legal syntax indeed, one that we can count on to be available in future PB-releases?