[RFA] linespec.c change to stop "malformed template specification" error

[Jim Blandy]

Elena Zannoni <ezannoni@cygnus.com> writes:
> Yes, you are correct. That function (find_toplevel_char) would get it wrong
> if we had something like this, even with Dan's patch:
> 
> break foo_class<x>y ? 1 : 2, 4>::foo
> 
> It would think that the greater-than was the end of the template, and
> that the ',' was outside of the template specification.  But, if that
> is a legal expression (I am not sure), how likely would it be?
> Definitely better with Dan's patch than w/o, at least we can catch the
> simpler cases.

Exactly.  We'll have to wait for a real parser before we can DTRT.