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

Eli Zaretskii
2009-06-01T15:46:09Z

> From: Thiago Jung Bauermann <bauerman@br.ibm.com>
> Cc: Tom Tromey <tromey@redhat.com>, Eli Zaretskii <eliz@gnu.org>,
> drow@false.org, pedro@codesourcery.com, gdb-patches@sourceware.org
> Date: Mon, 01 Jun 2009 00:56:51 -0300
>
> This patch implements such tri-state setting:
>
> (gdb) help set script-extension
> Set mode for script filename extension recognition.
> off == no filename extension recognition (all sourced files are GDB scripts)
> soft == evaluate script according to filename extension, fallback to GDB script
> hard == evaluate script according to filename extension, error if not supported
>
> The default is 'soft'. When Python support is not compiled in, the code
> always assumes a GDB script.
>
> Is this good enough for everybody?

Fine with me.

However, I would suggest "strict" instead of "hard".