Strings and Definitions

WinRad · 2008-08-10T15:23:55

Hey guys :), This question seems to be a very easy one but I couldn't find anything online to help me out so that's why I'm posting. Well now for the problem, when you have a definition such as - [code C++] #define Up 'W' and a function such as - [code Win32] GetAsyncKeyState(Up) - would it be the same as just saying/typing - [code Win32] GetAsyncKeyState('W') - ? Thanks a lot.

For Beginners

Started by WinRad August 09, 2008 08:40 PM

13 comments, last by SiCrane 15 years, 8 months ago

Spoonbender

1,258

August 10, 2008 04:43 AM

Quote:Original post by WinRad
Well that seems to make sense... Hmm but what if the macros I use are very long and specific and I only need them in one case? For example in my game I use a macro called Player1UpDef which is very specific and most likely would never be used by me again because I add def to the end of every #define macro.

Yes, then you're unlikely to get any name conflicts, so you're probably safe from that particular problem... But what did it buy you?
Why not just use the non-macro alternatives and be safe?

The point is that (almost) anything you do with macros, can be done as easily, and much much safer without them.

Quote:
Also I need to know the VK for the @ sign :).

As far as I know, all visible characters just use their ASCII code as VK.
A's virtual keycode is the integer value of 'A', and @'s is '@'.

WinRad

122

Author

August 10, 2008 05:15 AM

OK cool thank you :).

As with your "be safe" question. The reason I don't simply use variables is because the macros can be defined right at the top without any problems and I just find it easier to customize my app with macros then variables... because the variables end up cluterring so... well that's my reason.

Thanks again :).

bschneid

126

August 10, 2008 11:25 AM

Quote:Original post by WinRad
OK cool thank you :).

As with your "be safe" question. The reason I don't simply use variables is because the macros can be defined right at the top without any problems and I just find it easier to customize my app with macros then variables... because the variables end up cluterring so... well that's my reason.

Thanks again :).

A good design, most likely one that uses classes, would avoid the clutter that you speak of. Basically, if it works for you, fine, but don't think that clutter is a problem only solvable by an ugly work-around. Just something to remember.

theOcelot

498

August 10, 2008 02:54 PM

Quote:Original post by WinRad
As with your "be safe" question. The reason I don't simply use variables is because the macros can be defined right at the top without any problems and I just find it easier to customize my app with macros then variables... because the variables end up cluterring so... well that's my reason.

That's not a very good reason. Tell me why one of these is more cluttered than the other.

#define PI 3.14const double pi = 3.14;

What "problems" do you have with defining variables at the top? How much harder is it to change the value of a global constant than it is to change a #define? The benefits far outweigh the downsides of using real variables.

My Project: Somnopatru (SVN Repo) | Single Responsibility Principle | Other OOD articles

SiCrane

11,840

August 10, 2008 03:23 PM

Quote:Original post by Spoonbender
As far as I know, all visible characters just use their ASCII code as VK.
A's virtual keycode is the integer value of 'A', and @'s is '@'.

Virtual key codes are key codes. Assuming a standard US English keyboard, shift-2 would generate an '@'; however, the virtual key code generated would still be VK_2. If you wanted to check the characters generated by a key press you could try using WM_CHAR or WM_UNICHAR.

Strings and Definitions

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Strings and Definitions

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Reticulating splines