Re: [PATCH] Add support for embedding scripts in .debug_gdb_scripts.

[Eli Zaretskii <eliz@gnu.org>]

> Date: Fri, 16 Jan 2015 09:15:35 -0800
> From: Doug Evans <xdje42@gmail.com>
> Cc: binutils@sourceware.org, 	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
> 
> >> +* Python/Guile scripting
> >> +
> >> +** GDB now supports auto-loading of Python/Guile scripts contained in the
> >> +   special section named `.debug_gdb_scripts'.
> >
> > I think we should tell here on what systems/targets this is supported.
> > Otherwise, the NEWS entry is OK.
> 
> The previous news entry didn't, and I'm following that.

So we have no hope for ever fixing past mistakes?

> > Let's be consistent here" "null", lower-case and with 2 'l'.  This is
> > just a plain English word, not an acronym or a C symbol.
> 
> NULL is a typo, thanks for catching that.
> I'm just following usage elsewhere in gdb.texinfo,
> and I like this choice.

So we have no hope for ever fixing past mistakes?

> >> +The rest of the entry, up to the trailing NUL byte,
> >                                              ^^^
> > "null"
> 
> Copied from gdb.texinfo.
> Plus we've had this conversation before. :-)
> 
> https://sourceware.org/ml/gdb-patches/2013-12/msg00892.html
> https://sourceware.org/ml/gdb-patches/2013-12/msg00894.html

So we have no hope for ever fixing past mistakes?