comparison include/SDL_keyboard.h @ 911:04a403e4ccf5

Date: Mon, 3 May 2004 03:15:01 +0100 From: David Symmonds Subject: SDL Typedef Structs Hi, Thanks for the SDL libraries, I have been using them for about a year now and they are really brilliant. One thing that I have just found whilst using them through C++ (and needing forward declarations) is that when you typedef structs you sometimes use typedef struct Name { ... }Name; e.g. SDL_Surface and other times use typedef struct { ... }Name; e.g. SDL_Rect The first type works fine, when I define a header file I can just put 'struct Name;' at the top and use the Name throughout. However, the second type is harder to use in a header, and I haven't found a way yet, other than to include 'SDL.h' in the header file (undesirable). Would there be any harm in changing the definition of SDL_Rect and such like to the second form?
author Sam Lantinga <slouken@libsdl.org>
date Sun, 18 Jul 2004 22:57:40 +0000
parents b8d311d90021
children c9b51268668f
comparison
equal deleted inserted replaced
910:4ab6d1fd028f 911:04a403e4ccf5
53 ch = keysym.unicode & 0x7F; 53 ch = keysym.unicode & 0x7F;
54 } else { 54 } else {
55 An international character.. 55 An international character..
56 } 56 }
57 */ 57 */
58 typedef struct { 58 typedef struct SDL_keysym {
59 Uint8 scancode; /* hardware specific scancode */ 59 Uint8 scancode; /* hardware specific scancode */
60 SDLKey sym; /* SDL virtual keysym */ 60 SDLKey sym; /* SDL virtual keysym */
61 SDLMod mod; /* current key modifiers */ 61 SDLMod mod; /* current key modifiers */
62 Uint16 unicode; /* translated character */ 62 Uint16 unicode; /* translated character */
63 } SDL_keysym; 63 } SDL_keysym;