This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 2/2] Remove varobj_language_string, languages and varobj_languages
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Sat, 26 Oct 2013 08:09:11 +0400
- Subject: Re: [PATCH 2/2] Remove varobj_language_string, languages and varobj_languages
- Authentication-results: sourceware.org; auth=none
- References: <1382057576-19148-1-git-send-email-yao at codesourcery dot com> <1382057576-19148-2-git-send-email-yao at codesourcery dot com> <20131025041525 dot GC4769 at adacore dot com> <526A7407 dot 5090301 at codesourcery dot com>
> >I think this can do for now because it is good enough, but I would
> >definitely prefer we avoid this type transformation. Instead,
> >I'd rather we added a new field in struct language_defn that
> >provides the "natural" name.
> >
>
> I am OK to add a new field "la_varobj_name" in struct language_defn,
> but seems information is duplicated a little, we have both "c++" and
> "C++" in one language_defn.
It would not be a "varobj" name, but a "natural" name, that is the
name one would use when naming the language; eg: "Fortran 90" instead of
"f90". One possible analogy in our code base is the shortname/longname
distinction in struct target_ops.
--
Joel