upcoming changes in GDB parsing routines

[Joel Brobecker <brobecker at adacore dot com>]

Hello Insight developers,

I am working on adding a new field in the various parsing routines
inside GDB. Currently, these parsing routines use the global
current_language to determine which language to use in order
to do the parsing, but now I want the language to be specifically
specified.

Some of the routines that are about to be changed are being used
by insight, and once I commit the patch, insight will no longer build
because of the missing parameter.  The simple fix is to add
"current_language" as an extra argument at the end of the argument list
for all the calls that break. This should give you the exact same
behavior as before. You might want to take this opportunity to review
the use of current_language to see if it is appropriate or not. I
suspect it will. In GDB, we have situations where we are re-evaluating a
breakpoint expression that might have been set using a language that's
different from the current_language.

I can try to fix insight for you, althought I don't know if I have
permissions to, and I'm not sure whether I'll be able to build it
or not. I'll send a message to this mailing-list as soon as the
patch is committed.

Cheers,
-- 
Joel