@@ -1043,7 +1043,7 @@ static struct token *enum_specifier(struct token *token, struct symbol *sym, str
return ret;
}
-static void apply_ctype(struct position pos, struct ctype *src, struct ctype *dst);
+static void apply_ctype(struct position pos, struct ctype *dst, struct ctype *src);
static struct token *typeof_specifier(struct token *token, struct symbol *sym, struct decl_state *ctx)
{
@@ -1056,7 +1056,7 @@ static struct token *typeof_specifier(struct token *token, struct symbol *sym, s
struct symbol *sym;
token = typename(token->next, &sym, NULL);
ctx->ctype.base_type = sym->ctype.base_type;
- apply_ctype(token->pos, &sym->ctype, &ctx->ctype);
+ apply_ctype(token->pos, &ctx->ctype, &sym->ctype);
} else {
struct symbol *typeof_sym = alloc_symbol(token->pos, SYM_TYPEOF);
token = parse_expression(token->next, &typeof_sym->initializer);
@@ -1427,7 +1427,7 @@ static struct token *generic_qualifier(struct token *next, struct symbol *sym, s
return next;
}
-static void apply_ctype(struct position pos, struct ctype *src, struct ctype *dst)
+static void apply_ctype(struct position pos, struct ctype *dst, struct ctype *src)
{
unsigned long mod = src->modifiers;
@@ -1529,7 +1529,7 @@ static struct token *declaration_specifiers(struct token *token, struct decl_sta
break;
seen |= Set_S | Set_T;
ctx->ctype.base_type = s->ctype.base_type;
- apply_ctype(token->pos, &s->ctype, &ctx->ctype);
+ apply_ctype(token->pos, &ctx->ctype, &s->ctype);
token = token->next;
continue;
}
apply_ctype()'s argument order confuse me endlessly as I'm much more used to have the destination first and the source next (the so called 'assignment order' used for assignments but also in memcpy() and in many sparse or library functions). So, change the argument order of apply_ctype() to mimic the order of memcpy()/assignment, to hopefully reduce my confusion. Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com> --- parse.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)