This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH 7/7] Allow setting a parameter to raise gdb.GdbError

From: Tom Tromey <tom at tromey dot com>
To: Eli Zaretskii <eliz at gnu dot org>
Cc: Simon Marchi <simark at simark dot ca>, tom at tromey dot com, gdb-patches at sourceware dot org
Date: Mon, 24 Sep 2018 04:24:07 -0600
Subject: Re: [PATCH 7/7] Allow setting a parameter to raise gdb.GdbError
References: <20180915072459.14934-1-tom@tromey.com> <20180915072459.14934-8-tom@tromey.com> <83va77i0ko.fsf@gnu.org> <6385b06c-ec1a-3e6e-6b81-a4c0f4097556@simark.ca> <83lg7rbcc8.fsf@gnu.org>

>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:

Eli> So I think we should not use this paradigm here, to keep the confusion
Eli> level down.

FWIW I made the requested change before pushing:

>> >> +If this method raises @code{gdb.GdbError} (@pxref{Exception

>> > "raises the 'gdb.GdbError' exception", I presume?

However I wonder if it should read "a" rather the "the".

Tom

Follow-Ups:
- Re: [PATCH 7/7] Allow setting a parameter to raise gdb.GdbError
  - From: Eli Zaretskii

References:
- [PATCH 0/7] some small python fixes (one including a doc patch)
  - From: Tom Tromey
- [PATCH 7/7] Allow setting a parameter to raise gdb.GdbError
  - From: Tom Tromey
- Re: [PATCH 7/7] Allow setting a parameter to raise gdb.GdbError
  - From: Eli Zaretskii
- Re: [PATCH 7/7] Allow setting a parameter to raise gdb.GdbError
  - From: Simon Marchi
- Re: [PATCH 7/7] Allow setting a parameter to raise gdb.GdbError
  - From: Eli Zaretskii

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]