xkbcomp: Changes to 'master'

[Daniel Stone]

 keycodes.c   |   16 ++----
 parseutils.c |   10 ++--
 parseutils.h |    6 +-
 symbols.c    |    9 ++-
 xkbcomp.c    |    2 
 xkbcomp.h    |    2 
 xkbparse.y   |   53 +++++++---------------
 xkbscan.c    |  142 ++++++++++++++++++++++++++++++++++-------------------------
 8 files changed, 125 insertions(+), 115 deletions(-)

New commits:
commit 0b04ecbb7a6afb223c91d3b15baab0bc48542281
Author: Daniel Stone <daniel at fooishbar.org>
Date:   Tue Jun 15 19:26:19 2010 +0100

    Fix gcc warnings
    
    It was right too: printf was being misused in some spots.
    
    Signed-off-by: Daniel Stone <daniel at fooishbar.org>

commit 41b0857c8c1179b87a26888588cbfff28f8bb0d6
Author: Daniel Stone <daniel at fooishbar.org>
Date:   Tue Jun 8 15:11:19 2010 +0100

    Don't malloc() and free() most scanned symbols
    
    Use a constant buffer.  Sigh.
    
    Signed-off-by: Daniel Stone <daniel at fooishbar.org>

commit 7f7a57c75beb5e1dfb53351e490ef00a324b2727
Author: Daniel Stone <daniel at fooishbar.org>
Date:   Tue Jun 8 12:14:00 2010 +0100

    Fix compilation with DEBUG
    
    Signed-off-by: Daniel Stone <daniel at fooishbar.org>

commit 9887842e33174a6e98675b912e419c711dd20c0f
Author: Daniel Stone <daniel at fooishbar.org>
Date:   Mon Jun 7 22:45:13 2010 +0100

    Use fread() instead of getc()
    
    So, it turns out that if you're parsing a fairly large amount of data,
    using getc() to get all the input rather than, say, read(), is some kind
    of remarkably daft and unperformant idea.
    
    Signed-off-by: Daniel Stone <daniel at fooishbar.org>

commit 02de53d767b20bab1517b4e8a3e7eb3b9e7f15be
Author: Daniel Stone <daniel at fooishbar.org>
Date:   Mon Jun 7 22:43:01 2010 +0100

    Lazy keysym parsing (avoid XStringToKeysym)
    
    Instead of calling XStringToKeysym on every keysym we parse, store it as
    a string until we need to store it in an actual keymap.
    
    Signed-off-by: Daniel Stone <daniel at fooishbar.org>