const string = chr() & chr() is picky

[Zytan]

I am trying to set a const string made up of Chr(), but if the value
passed into Chr() is too large, the compiler complains that it is not
constant!! Example:

Public Const m_Data As String = Chr(&HD) & Chr(&HE) 'ok
Public Const m_Data As String = Chr(&HD0) & Chr(&HE0) 'not ok

But, Char stores 0..255, so it should be ok in both cases. What's
going on?

Zytan

[Herfried K. Wagner [MVP]]

"Zytan" <zy**********@y ahoo.comschrieb :

>I am trying to set a const string made up of Chr(), but if the value
passed into Chr() is too large, the compiler complains that it is not
constant!! Example:

Public Const m_Data As String = Chr(&HD) & Chr(&HE) 'ok
Public Const m_Data As String = Chr(&HD0) & Chr(&HE0) 'not ok

But, Char stores 0..255, so it should be ok in both cases. What's
going on?

Note that 'Chr' uses Windows ANSI. Maybe it's better to use 'ChrW', which
is Unicode-enabled, instead.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>

[Martin H.]

Hello Zytan,

Public Const m_Data As String = Chr(&HD) & Chr(&HE) 'ok
Public Const m_Data As String = Chr(&HD0) & Chr(&HE0) 'not ok

But, Char stores 0..255, so it should be ok in both cases. What's
going on?

It might be a Unicode issue. Try ChrW instead.

Best regards,

Martin

[Zytan]

Note that 'Chr' uses Windows ANSI. Maybe it's better to use 'ChrW', which

is Unicode-enabled, instead.

You are completely right. I knew the above, but i didn't think it
mattered. I was thinking ChrW() would return a two byte Char. Which
it does, and so does Chr(), since it's all unicode in VB .NET. Duh.

I still don't understand why it was complaining. I should note that
Chr() does accept 0..255, and I was within that range. So, something
is still wrong here.

But your suggestion works, so thanks!

Zytan

[Herfried K. Wagner [MVP]]

"Zytan" <zy**********@y ahoo.comschrieb :

>Note that 'Chr' uses Windows ANSI. Maybe it's better to use 'ChrW',
which
is Unicode-enabled, instead.

You are completely right. I knew the above, but i didn't think it
mattered. I was thinking ChrW() would return a two byte Char. Which
it does, and so does Chr(), since it's all unicode in VB .NET. Duh.

I still don't understand why it was complaining. I should note that
Chr() does accept 0..255, and I was within that range. So, something
is still wrong here.

'Chr' does not accept values greater than 127 when used in constants. The
reason is that 'Chr' would return different characters depending on the
system's Windows ANSI codepage for larger values. 'ChrW' always returns the
same character for a certain character code.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>

[Zytan]

'Chr' does not accept values greater than 127 when used in constants.

Sounds peculiar...

The
reason is that 'Chr' would return different characters depending on the
system's Windows ANSI codepage for larger values.

....until you said that.

'ChrW' always returns the
same character for a certain character code.

It all makes sense. And now that's something I'll remember. Again,
thanks for a very informative post, Herfried.

Zytan

[Zytan]

It might be a Unicode issue. Try ChrW instead.

>
Best regards,

Martin

Yup, thanks. Please read Herfried's very informative post for the
precise cause.

Zytan

[Zytan]

Note that 'Chr' uses Windows ANSI. Maybe it's better to use 'ChrW', which

is Unicode-enabled, instead.

Wait, luckily i had a debug.assert() to ensure things were ok, and i
found the following are not equivalent:

Dim a As String = Chr(&HD0) & Chr(&HE0)
Dim b As String = ChrW(&HD0) & ChrW(&HE0)

So, using ChrW(), while it allows b to be Const, where a cannot be
Const, it does not make b = a.

Zytan