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

[Joel Brobecker <brobecker@adacore.com>]

> > I do not like the cookie idea
> 
> Considering that this is the only alternative proposed so far that has
> the most chances to be accepted, and that it is 100% backwards
> compatible, perhaps you could reconsider.

Perhaps, but I believe that it makes the feature much much less useful
that it would be. I'd like to be able to grab a Python script, any
python script, and evaluate it in GDB.  For instance, if I have a Python
script that doesn't do anything GDB specific, I'd like to be able to
evaluate it without having to add the cookie.

I think that we're being much too strict in applying the compatibility
principle in this case.  I mean, what are the chances of someone naming
a GDB script with a .py extension? I think it's perfectly fine to tell
the few people who might have done so to rename their files (or stay
with GDB 6.x). We're not trying to be perfect, we're trying to do what's
going to be more useful in most cases.

-- 
Joel