From: James Pandavan <james.pandavan@googlemail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: gdb v7.0 - user defined command's document section - space prefixed end
Date: Tue, 03 Nov 2009 18:58:00 -0000 [thread overview]
Message-ID: <4AF07D60.2020305@googlemail.com> (raw)
In-Reply-To: <20091103143305.GN4573@adacore.com>
Joel Brobecker wrote:
> I'm not sure whether this change of behavior was intended or not. I wonder
> how many users indent their GDB scripts the way you did, with the "end"
> not being on the first column...
>
> For now, perhaps we should document the fact that we expect the "end"
> keyword to be on the first column of the line. I'm also wondering
> whether we should consider allowing white spaces before the end in
> the comment as well. It would make us backwards-compatible with
> previous versions.
>
>
I noticed my scripts didn't work under v7.0 only when I saw this bug in
launchpad. I guess I am not the only one who has indented "ends" this way :)
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/461594
I've also filed a bug report a day after I sent my original mail.
http://sourceware.org/bugzilla/show_bug.cgi?id=10868
next prev parent reply other threads:[~2009-11-03 18:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 6:12 James Pandavan
2009-11-03 14:33 ` Joel Brobecker
2009-11-03 18:58 ` James Pandavan [this message]
2009-11-03 19:43 ` Joel Brobecker
2009-11-03 19:51 ` Daniel Jacobowitz
2009-11-03 22:03 ` Jim Ingham
2009-11-06 21:42 ` Vladimir Prus
2009-11-06 21:49 ` Daniel Jacobowitz
2009-11-07 1:14 ` Vladimir Prus
2009-11-13 23:41 ` Daniel Jacobowitz
2009-11-19 7:17 ` Vladimir Prus
2009-11-04 20:47 ` Tom Tromey
2009-11-04 21:07 ` Paul Koning
2009-11-04 21:18 ` Joel Brobecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AF07D60.2020305@googlemail.com \
--to=james.pandavan@googlemail.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox