This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v2 4/4] introduce parallel mode
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 02 Aug 2013 22:38:12 +0300
- Subject: Re: [PATCH v2 4/4] introduce parallel mode
- References: <1375457773-863-1-git-send-email-tromey at redhat dot com> <1375457773-863-5-git-send-email-tromey at redhat dot com> <834nb8yntk dot fsf at gnu dot org> <87mwp0c52c dot fsf at fleche dot redhat dot com> <8338qsylu4 dot fsf at gnu dot org> <87iozoc4kf dot fsf at fleche dot redhat dot com> <831u6bzyuo dot fsf at gnu dot org> <87bo5fdho0 dot fsf at fleche dot redhat dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Tom Tromey <tromey@redhat.com>
> Cc: gdb-patches@sourceware.org
> Date: Fri, 02 Aug 2013 13:19:43 -0600
>
> Eli> Looks like it's a matter of taste in this case.
>
> If you really think @itemize is preferred here, I will comply.
I don't think it's preferred. I think both forms are about the same
in this case.
> I'd like to understand your rationale, though.
> If I were writing this from scratch I would not have even considered
> @itemize, but rather @table. I'd like to know when I ought to use
> @itemize in this scenario instead.
@itemize is a way to enumerate things. Which is what this text does.
@table is more suitable to a list of values of a single variable, or a
list of alternatives. Which is also what this text is about.