How to retrun a character with ascii code

[ad]

How to retrun a character with ascii code?
It is useChr(65) return 'A' in VB.NET.
What is the equivalent function in C#?

[Dmytro Lapshyn [MVP]]

Hi Ad,

char[] characters = System.Text.Encoding.ASCII.GetChars(new byte[] {65});

Yes, looks quite cumbersome and I wonder myself why there is no overload for
a single character (or was I just too lazy to dig MSDN enough? ;-)

--
Sincerely,
Dmytro Lapshyn [Visual Developer - Visual C# MVP]
"ad" <[e-mail]> wrote in message
news:ey**************@tk2msftngp13.phx.gbl...

How to retrun a character with ascii code?
It is useChr(65) return 'A' in VB.NET.
What is the equivalent function in C#?

[Oskar Punz]

Hallo!

<Dmytro Lapshyn [MVP]> schrieb...

Hi Ad,

char[] characters = System.Text.Encoding.ASCII.GetChars(new byte[]
{65});

Yes, looks quite cumbersome and I wonder myself why there is no
overload for a single character (or was I just too lazy to dig MSDN
enough? ;-)

Why not Convert.ToChar(65) ?

Sincerely

Oskar

[Joerg Jooss]

Oskar Punz wrote:

Hallo!

<Dmytro Lapshyn [MVP]> schrieb...

Hi Ad,

char[] characters = System.Text.Encoding.ASCII.GetChars(new byte[]
{65});

Yes, looks quite cumbersome and I wonder myself why there is no
overload for a single character (or was I just too lazy to dig MSDN
enough? ;-)

Why not Convert.ToChar(65) ?

char c = (char) 65;

works as well, though I consider it less readable.

Cheers,
--
http://www.joergjooss.de
mailto:ne********@joergjooss.de

[Dmytro Lapshyn [MVP]]

Hallo Oskar,

I think Convert.ToChar as well as (char)65 assume the Unicode encoding,
while the author has explicitly mentioned the ASCII one.
Yes, the character codes of the capital 'A' are the same in both of the
encodings, but this, in general, might be not true for other character codes
and other encodings.

--
Sincerely,
Dmytro Lapshyn [Visual Developer - Visual C# MVP]
"Oskar Punz" <da***************@utanet.at> wrote in message
news:u7**************@TK2MSFTNGP14.phx.gbl...

Hallo!

<Dmytro Lapshyn [MVP]> schrieb...

Hi Ad,

char[] characters = System.Text.Encoding.ASCII.GetChars(new byte[]
{65});

Yes, looks quite cumbersome and I wonder myself why there is no
overload for a single character (or was I just too lazy to dig MSDN
enough? ;-)

Why not Convert.ToChar(65) ?

Sincerely

Oskar

[Oskar Punz]

Hi!

<Dmytro Lapshyn [MVP]> schrieb...

Hallo Oskar,

I think Convert.ToChar as well as (char)65 assume the Unicode
encoding, while the author has explicitly mentioned the ASCII one.
Yes, the character codes of the capital 'A' are the same in both of
the encodings, but this, in general, might be not true for other
character codes and other encodings.

AFAIK the first 128 Unicode characters are the same as the
ASCII characters (except an extra leading zero byte).

So as long as you don't use values above 127 nothing
can go wrong. Right?

Ciao

Oskar

[James Curran]

For every character which has an ASCII code, it's the same in UNICODE
(expanded to 16-bits)

--
--
Truth,
James Curran
[erstwhile VC++ MVP]

Home: www.noveltheory.com Work: www.njtheater.com
Blog: www.honestillusion.com Day Job: www.partsearch.com

"Dmytro Lapshyn [MVP]" <x-****@no-spam-please.hotpop.com> wrote in message
news:ef*************@TK2MSFTNGP15.phx.gbl...

Hallo Oskar,

I think Convert.ToChar as well as (char)65 assume the Unicode encoding,
while the author has explicitly mentioned the ASCII one.
Yes, the character codes of the capital 'A' are the same in both of the
encodings, but this, in general, might be not true for other character codes and other encodings.

[J.Marsch]

Interesting read on the subject of character encoding:
http://www.joelonsoftware.com/articles/Unicode.html
"Oskar Punz" <da***************@utanet.at> wrote in message
news:OG**************@TK2MSFTNGP15.phx.gbl...

Hi!

<Dmytro Lapshyn [MVP]> schrieb...

Hallo Oskar,

I think Convert.ToChar as well as (char)65 assume the Unicode
encoding, while the author has explicitly mentioned the ASCII one.
Yes, the character codes of the capital 'A' are the same in both of
the encodings, but this, in general, might be not true for other
character codes and other encodings.

AFAIK the first 128 Unicode characters are the same as the
ASCII characters (except an extra leading zero byte).

So as long as you don't use values above 127 nothing
can go wrong. Right?

Ciao

Oskar