Re: RFC: add ability to "source" Python code

Eli Zaretskii
2009-02-11T21:46:33Z

> Date: Wed, 11 Feb 2009 16:14:18 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: tromey@redhat.com, brobecker@adacore.com, bauerman@br.ibm.com,
> pedro@codesourcery.com, gdb-patches@sourceware.org
>
> > Yes, this is called "backward compatibility". It just could be that
> > one reason why someone configures GDB without Python is that they
> > don't want this incompatible change.
>
> This argument would prevent us ever adding new commands or changing
> the behavior of a command without adding a configure option for them.

We are not adding a new command, we are modifying behavior of an old
one in a gratuitously incompatible way.

I don't mind adding a new command, because invoking nonexistent
commands generally produces an error. So chances of breaking existing
scripts are all but non-existent. But here we are talking about
breaking something that works today without any error message, and
that's another story.