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

Thiago Jung Bauermann
2009-02-10T11:58:24Z

El mar, 10-02-2009 a las 11:34 +0200, Eli Zaretskii escribiÃ³:
> > Date: Mon, 9 Feb 2009 22:48:34 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
> > > > I think you may be thinking of invoking a python script using
> > > > "#!.../gdb -something". This patch does not cover that case. That is
> > > > a separate patch, which I haven't submitted.
> >
> > I had something like "# *-python-*" in mind... :-)
>
> Yes. I think this is by far the best solution, one that will keep
> back compatibility without hampering any of the new and valuable
> Python features.
>
> Can we agree on using such cookies in GDB scripts written in Python?
> Then we won't need the -p switch or the .py extension detection.

I don't mind GDB detecting that string in the beginning of a Python
script. But I am strongly against dropping filename extension detection
in favour of that.

I've never written a Python script (in GDB or otherwise) with that
markup, but *all* the Python scripts I ever wrote in my life ended
in .py. It'd be just counter-intuitive and counter productive to not
support the filename extension.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center