From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-76007-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 14092 invoked by alias); 9 Oct 2010 09:14:27 -0000
Received: (qmail 14082 invoked by uid 22791); 9 Oct 2010 09:14:26 -0000
X-SWARE-Spam-Status: No, hits=-0.9 required=5.0	tests=AWL,BAYES_00,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Received: from mtaout20.012.net.il (HELO mtaout20.012.net.il) (80.179.55.166)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 09 Oct 2010 09:14:21 +0000
Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0LA000M00MTZOC00@a-mtaout20.012.net.il> for gdb-patches@sourceware.org; Sat, 09 Oct 2010 11:14:18 +0200 (IST)
Received: from HOME-C4E4A596F7 ([84.229.148.82]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LA000L6XMZSXHE0@a-mtaout20.012.net.il>; Sat, 09 Oct 2010 11:14:17 +0200 (IST)
Date: Sat, 09 Oct 2010 09:14:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFA] New python module gdb.types
In-reply-to: <AANLkTi=P7-+0grj3jhjDVaeHDQwey6JpkS+GZDQwP9w-@mail.gmail.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <83tykvn2xh.fsf@gnu.org>
References: <20101006204434.DCD842461B2@ruffy.mtv.corp.google.com> <83vd5fnicu.fsf@gnu.org> <AANLkTi=P7-+0grj3jhjDVaeHDQwey6JpkS+GZDQwP9w-@mail.gmail.com>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2010-10/txt/msg00172.txt.bz2

> Date: Fri, 8 Oct 2010 15:18:45 -0700
> From: Doug Evans <dje@google.com>
> Cc: gdb-patches@sourceware.org
> 
> Return @var{type} with const and volatile qualifiers stripped,
> and with typedefs and references converted to the underlying type.

If the conversion of typedefs is recursive, then I think "to the
underlying primitive data type" is more accurate.

This takes care of typedefs.  I'm still unclear regarding the
"references" part.  What does it mean? removing the "pointer to" part,
like in "int *" -> "int"?

I still maintain that examples go a long way towards explaining such
abstract descriptions.

> >> +@item make_enum_dict (@var{enum_type})
> >> +Return a dictionary made from @var{enum_type}.
> >
> > Same here: at the very least we should say what is a "dictionary" in
> > this context.
> 
> The context is python and in the python context "dictionary" is quite
> specific, it's a builtin type.

Well, you used it as a simple word, which makes it hard to guess to
someone like me, for whom Python is a read-only language.

> What if it said the following instead?
> 
> Return a python dictionary made from @var{enum_type}.

How about

  Return a Python @code{dictionary} type produced from @var{enum_type}.