summaryrefslogtreecommitdiff
path: root/include/SDL_keyboard.h
diff options
context:
space:
mode:
authorSam Lantinga <slouken@libsdl.org>2004-07-18 22:57:40 +0000
committerSam Lantinga <slouken@libsdl.org>2004-07-18 22:57:40 +0000
commitae42198c26977a26c6e1c01d04ae73e652ef98e9 (patch)
treefba8c57821d9cf334aaa404b0b0807301aed9c22 /include/SDL_keyboard.h
parent4662e8cdc6778b0cad95ffd022c64e4cc1c8965a (diff)
downloadsdl-ae42198c26977a26c6e1c01d04ae73e652ef98e9.tar.gz
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?
Diffstat (limited to 'include/SDL_keyboard.h')
-rw-r--r--include/SDL_keyboard.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/include/SDL_keyboard.h b/include/SDL_keyboard.h
index b45080ed3..263d198ac 100644
--- a/include/SDL_keyboard.h
+++ b/include/SDL_keyboard.h
@@ -55,7 +55,7 @@ extern "C" {
An international character..
}
*/
-typedef struct {
+typedef struct SDL_keysym {
Uint8 scancode; /* hardware specific scancode */
SDLKey sym; /* SDL virtual keysym */
SDLMod mod; /* current key modifiers */