If, for some weird reason, you _have_ to use Hungarian in .NET, at least use it properly
-
-
-
OK, I should've used the joke icon. If you take a look at my profile, I'm from Hungary. The joke was based upon the fact that Hungarian is not the same as Hungarian Notation.
-
Hey, give the guy/gal a break. At least the variables have been initialised. :)
Chris Meech I am Canadian. [heard in a local bar]
-
Well, accept for the naming this is not a coding horror. If he was coding for Windows before Vista, he would even be correct. The reason being that with VC6, and any compiler that created 32 bit code, an
intand alongwhere the same thing. I am not sure about alongbut anintis supposed to be a machine word. In reality it depends on the compiler being used.INTP "Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra
-
Well, accept for the naming this is not a coding horror. If he was coding for Windows before Vista, he would even be correct. The reason being that with VC6, and any compiler that created 32 bit code, an
intand alongwhere the same thing. I am not sure about alongbut anintis supposed to be a machine word. In reality it depends on the compiler being used.INTP "Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra
But Hungarian notation used the l (or lng for the VBized version) to denote longs. Take this as an example, lpszMyText which stands for a Long Pointer to a String terminated by a Zero.
Deja View - the feeling that you've seen this post before.
-
But Hungarian notation used the l (or lng for the VBized version) to denote longs. Take this as an example, lpszMyText which stands for a Long Pointer to a String terminated by a Zero.
Deja View - the feeling that you've seen this post before.
Do you know what a long pointer is? I do. Hungarian notation has its uses, but it falls way short of what it was intended to do. In the case presented an
intis probably 32 bit and anlongis probably 32 bits, so coding wise it makes no difference until you start using a 64 bit compiler, in which case they will probably both be the same again.INTP "Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra
-
Do you know what a long pointer is? I do. Hungarian notation has its uses, but it falls way short of what it was intended to do. In the case presented an
intis probably 32 bit and anlongis probably 32 bits, so coding wise it makes no difference until you start using a 64 bit compiler, in which case they will probably both be the same again.INTP "Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra
John R. Shaw wrote:
Do you know what a long pointer is? I do.
So do I (having a C/C++ background here). However, it is worth noting that there is a difference in the maximum/minimum allowed values between an int and a long. Try this in C#
Console.WriteLine(int.MaxValue.ToString()); Console.WriteLine(long.MaxValue.ToString());So, look at the code again and tell me - do you think that an int and a long can be treated the same here?
Deja View - the feeling that you've seen this post before.
-
A fragment found indicating a similar naming blunder encountered in our code... szCallerName.GetBuffer(0) :wtf:
-
John R. Shaw wrote:
Do you know what a long pointer is? I do.
So do I (having a C/C++ background here). However, it is worth noting that there is a difference in the maximum/minimum allowed values between an int and a long. Try this in C#
Console.WriteLine(int.MaxValue.ToString()); Console.WriteLine(long.MaxValue.ToString());So, look at the code again and tell me - do you think that an int and a long can be treated the same here?
Deja View - the feeling that you've seen this post before.
LOL! Sorry I tend not to notice the ‘.Net’ reference when looking at code that appears to be C or C++. Try that same logic in C or C++ and you will see it does not apply. When computers used 16 bit words an ‘int’ was supposed to be 16 bits as per language specifications (but actually it depended on the compiler). When they changed to 32 bit words (size of register) and new compilers came out, then ‘int’ became 32 bits per language specifications, which made it the same as a long. I do not know what artificial limits C# uses, but C and C++ uses register size and the compiler vendor sets the limits according to the standard. Any code you develop should be archived along with a copy of the compiler (environment) and the associated libraries, so that it can be recreated without having to modify it.
INTP "Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra
-
Do you know what a long pointer is? I do. Hungarian notation has its uses, but it falls way short of what it was intended to do. In the case presented an
intis probably 32 bit and anlongis probably 32 bits, so coding wise it makes no difference until you start using a 64 bit compiler, in which case they will probably both be the same again.INTP "Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra
John R. Shaw wrote:
Do you know what a long pointer is? I do.
long pointers are used to access memory that is located in the other segment(intersegment). Am I right?
Regards, Arun Kumar.A
-
LOL! Sorry I tend not to notice the ‘.Net’ reference when looking at code that appears to be C or C++. Try that same logic in C or C++ and you will see it does not apply. When computers used 16 bit words an ‘int’ was supposed to be 16 bits as per language specifications (but actually it depended on the compiler). When they changed to 32 bit words (size of register) and new compilers came out, then ‘int’ became 32 bits per language specifications, which made it the same as a long. I do not know what artificial limits C# uses, but C and C++ uses register size and the compiler vendor sets the limits according to the standard. Any code you develop should be archived along with a copy of the compiler (environment) and the associated libraries, so that it can be recreated without having to modify it.
INTP "Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra
John R. Shaw wrote:
Try that same logic in C or C++ and you will see it does not apply.
I know - this caught me out a few times when I first moved over to .NET. I must admit that it really bugged me - especially when attempting to convert values. .NET standardised on int being Int32 and long being Int64.
Deja View - the feeling that you've seen this post before.
-
John R. Shaw wrote:
Try that same logic in C or C++ and you will see it does not apply.
I know - this caught me out a few times when I first moved over to .NET. I must admit that it really bugged me - especially when attempting to convert values. .NET standardised on int being Int32 and long being Int64.
Deja View - the feeling that you've seen this post before.
What really bugs me some times is that even though the C and C++ languages are standardized the size of the types are not. That is even the size of ‘char’ is not guaranteed to be a byte, at least that is what Bjarne Stroustrup says and he should know.
INTP "Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra
-
John R. Shaw wrote:
Do you know what a long pointer is? I do.
long pointers are used to access memory that is located in the other segment(intersegment). Am I right?
Regards, Arun Kumar.A
Actually no! Long pointers are not used any more and where used to overcome the limitations of PC memory access. The PC was limited to accessing only 64k, minus a few bytes for the systems use, so that was the max you could allocate with standard C (malloc). A normal pointer was only 16 bits, and a long pointer was a 32 bit pointer which required the compiler to generate code that allowed you to access more that 64k. Microsoft had the keyword ‘_far’ which told the compiler to make the pointer 32 bits instead of 16 bits and generate the required code. When Windows 95 came along and VC6 came out the ‘_far’ keyword was no longer supported, because it was not longer needed. All the ‘lp’ references in the code no longer mattered because all the pointers where now the same size, but if your previous code used the macro definitions like ‘LPSTR’ then it would still compile without error because the macros had been changed. If you had used the keyword ‘_far’ in any of your code, then you had to go in and remove it so you could compile the same code on the new compiler. That is pretty much it, ‘lp’ means ‘p’ now days.
INTP "Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra
-
Actually no! Long pointers are not used any more and where used to overcome the limitations of PC memory access. The PC was limited to accessing only 64k, minus a few bytes for the systems use, so that was the max you could allocate with standard C (malloc). A normal pointer was only 16 bits, and a long pointer was a 32 bit pointer which required the compiler to generate code that allowed you to access more that 64k. Microsoft had the keyword ‘_far’ which told the compiler to make the pointer 32 bits instead of 16 bits and generate the required code. When Windows 95 came along and VC6 came out the ‘_far’ keyword was no longer supported, because it was not longer needed. All the ‘lp’ references in the code no longer mattered because all the pointers where now the same size, but if your previous code used the macro definitions like ‘LPSTR’ then it would still compile without error because the macros had been changed. If you had used the keyword ‘_far’ in any of your code, then you had to go in and remove it so you could compile the same code on the new compiler. That is pretty much it, ‘lp’ means ‘p’ now days.
INTP "Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra
Thank you very much for your reply. But, in C Language, how to access the memory 0xb8000000 which is the memory address for VDU. Similarly , how to execute the POST function located at 0xffff000 without far pointer?
Regards, Arun Kumar.A
-
What really bugs me some times is that even though the C and C++ languages are standardized the size of the types are not. That is even the size of ‘char’ is not guaranteed to be a byte, at least that is what Bjarne Stroustrup says and he should know.
INTP "Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra
Thank god for sizeof I say.
Deja View - the feeling that you've seen this post before.
-
Thank god for sizeof I say.
Deja View - the feeling that you've seen this post before.
You do know that ‘sizeof’ returns a number based on the ‘char’ size don’t you. Therefore if the character size was 16 bits then ‘sizeof(char)’ would still be 1 and not the number of bytes. Isn’t non-specific specifications wonderful. :laugh:
INTP "Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra
-
Thank you very much for your reply. But, in C Language, how to access the memory 0xb8000000 which is the memory address for VDU. Similarly , how to execute the POST function located at 0xffff000 without far pointer?
Regards, Arun Kumar.A
Now days:
unsigned char* p = (unsigned char*)0xB8000000L;Old days:unsigned char _far* p = (unsigned char _far*)0xB8000000L;Used to do stuff like that all the time to directly access video memory and other hardware, but modern operating systems do not allow that any more. Accept for older code, which it places in a sandbox (its own processing space) so it can keep an eye on it, and even then it may not allow it. Direct access now requires a driver down at ring 0 to access hardware directly, but there is usually something like DirectX that does it for you. Note that both the addresses you mentioned are 32 bit and are therefore just ordinary pointers on a 32 bit machine.INTP "Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra
-
Now days:
unsigned char* p = (unsigned char*)0xB8000000L;Old days:unsigned char _far* p = (unsigned char _far*)0xB8000000L;Used to do stuff like that all the time to directly access video memory and other hardware, but modern operating systems do not allow that any more. Accept for older code, which it places in a sandbox (its own processing space) so it can keep an eye on it, and even then it may not allow it. Direct access now requires a driver down at ring 0 to access hardware directly, but there is usually something like DirectX that does it for you. Note that both the addresses you mentioned are 32 bit and are therefore just ordinary pointers on a 32 bit machine.INTP "Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra
Thank you very much. :):):)
Regards, Arun Kumar.A