unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Panicz Maciej Godek <godek.maciek@gmail.com>
To: John Darrington <john@darrington.wattle.id.au>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: docstrings in the reference manual
Date: Tue, 16 Dec 2014 13:18:49 +0100	[thread overview]
Message-ID: <CAMFYt2YsRp=iJ_TFTeJfkMX5Au6wgX_pYdHg7Th8PNb-B-qPVA@mail.gmail.com> (raw)
In-Reply-To: <20141216114248.GA4960@intra>

[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]

2014-12-16 12:42 GMT+01:00 John Darrington <john@darrington.wattle.id.au>:
>
> Why murder the English language more than necessary?  "Docstrings" is a
> cliche
> which has come from other projects.  Peope for whom English is not their
> first
> language can be confused by such aliterations.  They won't find the word
> in any
> dictionary.
>
>
Actually, there's a wikipedia entry regarding that notion:
http://en.wikipedia.org/wiki/Docstring
It appears that the word 'docstring' is already used in the technical
jargon and Jamil's case proves that the manual could do better in
faciliating the search.

Write the term "documentation string" out in full, or simply "documentation"
> where the context is clear.


If you take a look at the index of the manual, you'll find entries like:
"alist", "async", "errno", "smob", "vcell" and so on. I don't think that
adding a "docstring" entry would do any harm in this particular context (on
the other hand, the "documentation string" entry is lacking as well, so I
agree that it is more important to add this one in the first place)

[-- Attachment #2: Type: text/html, Size: 1907 bytes --]

  reply	other threads:[~2014-12-16 12:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15 22:48 docstrings in the reference manual jamil egdemir
2014-12-16  6:50 ` Panicz Maciej Godek
2014-12-16 10:54   ` jamil egdemir
2014-12-16 11:41     ` Panicz Maciej Godek
2014-12-16 11:42     ` John Darrington
2014-12-16 12:18       ` Panicz Maciej Godek [this message]
2014-12-16 20:16         ` jamil egdemir

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMFYt2YsRp=iJ_TFTeJfkMX5Au6wgX_pYdHg7Th8PNb-B-qPVA@mail.gmail.com' \
    --to=godek.maciek@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=john@darrington.wattle.id.au \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).