Re: [RFA 7/9] Explicit locations v2 - CLI for explicit locations

[Matt Rice <ratmice@gmail.com>]

On Thu, May 8, 2014 at 11:03 AM, Keith Seitz <keiths@redhat.com> wrote:
> Hi,
>
> This patch starts exposing these new features to users. This patch adds the
> ability to specify explicit locations via the CLI:
>
>         (explicit_location_lex_one): New function.

+static char *
+explicit_location_lex_one (const char **inp,
+               const struct language_defn *language)
+{
....
+      /* If quoted, skip to the ending quote.  */
+      if (strchr (get_gdb_linespec_parser_quote_characters (), *start))

Just curious if we need this quote handling in explicit linespec's

I thought (though i'm not terribly familiar with c++ linespecs)
that the quotes were for operator+, clashing with foo+offset
and 'something::foo' clashing with file:line stuff,

where it isn't obvious to me the need for it arises when using
explicit locations.
I suppose break -source '/path with spaces/foo.c' -line +42

my main curiosity here is for languages which allow the ' character,
particularly the ML family's usage of type variables[1]. to
discriminate polymorphic functions of the variety break -function
foo('a) vs break -function foo(string).

Given that this isn't really a language gdb currently supports or that
anyone is attempting to add support for (to my knowledge) consider it
with whatever priority you deem appropriate.

I Suppose the above -source style of quoting would push ML support
further in the direction of the ada specific code underneath what i'd
quoted above... hmm

http://en.wikipedia.org/wiki/Type_variable