Or if he wants unicode, which you normally would in .NET ...
The poster specifically asked how he could convert the Asc
function to C#. That, to me, suggests that he wants to translate
existing, working code, rather than creating something new from
scratch in order to satisfy someone's requirements for doing things
the "right" way.
If he wants *exactly* the same conversion, he can copy the
whole function (thereby avoiding having to include the namespace)
or - if the characters are known to be <0x80, get equivalent
functionality by grabbing the first part only.
So as I see it, there are two discussions going on in this thread:
How to do a direct translation or how to obtain similar results
some other way. Any of the latter would require testing and
documentation of differences in behavior.
If the requirement is Asc with Asc being what it is, then I fail
to see how int(c) alone would satisfy this requirement?!?
But as you can see from using .Net Reflector (below), the full
Asc(char) function is a little more elaborate than that.
public static int Asc(char String)
{
int num;
int num2 = Convert.ToInt32(String);
if (num2 < 0x80)
{
return num2;
}
try
{
byte[] buffer;
Encoding fileIOEncoding = Utils.GetFileIOEncoding();
char[] chars = new char[] { String };
if (fileIOEncoding.IsSingleByte)
{
buffer = new byte[1];
int num3 = fileIOEncoding.GetBytes(chars, 0, 1, buffer,
0);
return buffer[0];
}
buffer = new byte[2];
if (fileIOEncoding.GetBytes(chars, 0, 1, buffer, 0) == 1)
{
return buffer[0];
}
if (BitConverter.IsLittleEndian)
{
byte num4 = buffer[0];
buffer[0] = buffer[1];
buffer[1] = num4;
}
num = BitConverter.ToInt16(buffer, 0);
}
catch (Exception exception)
{
throw exception;
}
return num;
}
Yuck - a piece of code.
Do you dislike code examples in general or just that piece
of code?
I did not write it. That is what it looks like in the framework
(never mind the variable names).
Regards,
Joergen Bech
