eolian: schar and uchar are now called byte and ubyte, char stays

Here, 'char' represents an actual character and is meant to be treated as so by generators.
The byte types represent a numerical value and should be treated numerically.
This commit is contained in:
Daniel Kolesa 2014-07-14 16:25:26 +01:00
parent 10ea6e9f0f
commit f510b6de72
2 changed files with 5 additions and 6 deletions

View File

@ -51,9 +51,8 @@ static const char * const tokens[] =
static const char * const ctypes[] =
{
"char", "unsigned char", "signed char", "short", "unsigned short",
"int", "unsigned int", "long", "unsigned long", "long long",
"unsigned long long",
"signed char", "unsigned char", "char", "short", "unsigned short", "int",
"unsigned int", "long", "unsigned long", "long long", "unsigned long long",
"int8_t", "uint8_t", "int16_t", "uint16_t", "int32_t", "uint32_t",
"int64_t", "uint64_t", "int128_t", "uint128_t",
@ -480,14 +479,14 @@ eo_lexer_keyword_str_get(int kw)
Eina_Bool
eo_lexer_is_type_keyword(int kw)
{
return (kw >= KW_char && kw <= KW_void);
return (kw >= KW_byte && kw <= KW_void);
}
const char *
eo_lexer_get_c_type(int kw)
{
if (!eo_lexer_is_type_keyword(kw)) return NULL;
return ctypes[kw - KW_char];
return ctypes[kw - KW_byte];
}
static int _init_counter = 0;

View File

@ -24,7 +24,7 @@ enum Tokens
KW(type), KW(values), KWAT(in), KWAT(inout), KWAT(nonull), KWAT(out), \
KWAT(warn_unused), \
\
KW(char), KW(uchar), KW(schar), KW(short), KW(ushort), KW(int), KW(uint), \
KW(byte), KW(ubyte), KW(char), KW(short), KW(ushort), KW(int), KW(uint), \
KW(long), KW(ulong), KW(llong), KW(ullong), \
\
KW(int8), KW(uint8), KW(int16), KW(uint16), KW(int32), KW(uint32), \