From 0f6702adbc7792499fba6d2fb067fb817a603fd6 Mon Sep 17 00:00:00 2001 From: Kaz Kylheku Date: Tue, 1 Sep 2020 06:51:35 -0700 Subject: tags: address small issue with tag lookup. Exuberant Ctags uses the full content of one line as the key to find a tag. A function declaration that is split into multiple lines can have a first line which is identical to the definition, as in: static int add(int a, int b); static int add(int a, int b) { return a + b; } Here, the search key which ctags uses for the add function is "static int add(int a,", taken from the definition. But it's exactly the same as a the first line of the declaration, and that is what Vim jumps to for that tag. A few function declarations in TXR have this issue. * eval.c (expand_params_rec, do_eval): Make the first line of the forward declaration different from the first line of the definition. * match.c (mf_all): Likewise. * struct.c (make_struct_type_compat): Likewise. --- eval.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'eval.c') diff --git a/eval.c b/eval.c index de2acf92..6752ad18 100644 --- a/eval.c +++ b/eval.c @@ -984,8 +984,8 @@ static val make_var_shadowing_env(val menv, val vars); static val get_param_syms(val params); -static val expand_params_rec(val params, val menv, - val macro_style_p, val form); +static val expand_params_rec(val params, val menv, val macro_style_p, + val form); static val expand_opt_params_rec(val params, val menv, val macro_style_p, val form) @@ -1431,8 +1431,8 @@ nil_out: return nil; } -static val do_eval(val form, val env, val ctx, - val (*lookup)(val env, val sym)); +static val do_eval(val form, val env, + val ctx, val (*lookup)(val env, val sym)); static void do_eval_args(val form, val env, val ctx, val (*lookup)(val env, val sym), -- cgit v1.2.3