unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: Mark Harig <idirectscm@aim.com>
Cc: bug-guile@gnu.org, Ralf.Wildenhues@gmx.de
Subject: Re: Typos in the manual
Date: Thu, 17 Feb 2011 00:10:28 +0000	[thread overview]
Message-ID: <87vd0jwmff.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <8CD9B9D3EC85D3A-714-4D4E@webmail-d099.sysops.aol.com> (Mark Harig's message of "Tue, 15 Feb 2011 22:03:39 -0500")

Mark Harig <idirectscm@aim.com> writes:

> Some of the discussion below was getting too far off-topic [...]

Hi Mark,

Your development of the argument below is interesting, and I think it
could be an interesting discussion to have.  In this email, though, I
just wanted to mention a couple of points, one of which I think I didn't
get quite right in my previous reply.

>> > Something that's long been a mystery to me is why it is that 
> computer
>> > programmers, who spend their days learning and following the rules 
> and
>> > idioms of various programming languages, do not want to learn and
>> > follow the rules and idioms of natural languages.
>>
>> Because computer languages are constrained by the specifications and
>> tools that interpret them, whereas natural languages evolve and 
> diverge
>> through human usage?

When I read your para above before, it (strangely) didn't occur to me
that it could be intended to include reference to me and the Guile
manual.  Hence my general reply above, about the practical constraints
on computer language evolution being tighter than those on human
languages.

Now that that does occur to me, I see that my reply could be read as
implying "yes, I am knowingly not learning and following the rules...".

Just to be clear then, I didn't mean to imply that.  In fact I believe
that I and the Guile manual do "follow the rules and idioms of natural
languages."  Note in particular that this thread about "i.e.," is
nothing to do with the looseness of human language constraints (i.e.,
the kind of thing that allows many people today to say "you was" rather
than "you were").  It's to do with a convention that has forked in two
standard forms of English.

> 4) Programmers develop strong opinions about what is ugly or clean
> in computer languages, despite the fact that this is not described in
> the
> language specifications.  Yet, when something is pointed out as clean
> or ugly in natural language, that developed sense is dismissed.

When you say "dismissed", are you including this thread, and/or Guile
manual discussions in general?

Regards,
        Neil



  parent reply	other threads:[~2011-02-17  0:10 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-08 20:25 Typos in the manual Ralf Wildenhues
2011-02-13  0:49 ` Neil Jerram
2011-02-13  7:00   ` Ralf Wildenhues
2011-02-13 22:29     ` Neil Jerram
2011-02-15 15:48     ` Marijn
2011-02-15 20:21       ` Mark Harig
2011-02-15 23:55         ` Neil Jerram
2011-02-16  0:52           ` Mark Harig
2011-02-16 22:37             ` Neil Jerram
2011-02-15 23:49       ` Neil Jerram
2011-02-15 20:48   ` Mark Harig
2011-02-15 21:14     ` Ralf Wildenhues
2011-02-15 22:32       ` Mark Harig
2011-02-16  0:14         ` Neil Jerram
2011-02-16  2:43           ` Mark Harig
2011-02-16  3:30             ` Francis Southern
2011-02-16 23:46               ` Neil Jerram
2011-02-16  3:03           ` Mark Harig
2011-02-16  8:18             ` Thien-Thi Nguyen
2011-02-17  0:10             ` Neil Jerram [this message]
2011-02-17  1:21               ` Mark Harig
2011-02-16 21:17         ` Ludovic Courtès
2011-02-17  0:14           ` Neil Jerram
2011-02-17  3:13           ` Mark Harig
2011-02-17 11:33             ` Andy Wingo
2011-02-21 20:23             ` Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2011-02-19 17:40 Bruno Haible
2011-02-19 17:56 ` Ralf Wildenhues
2011-02-24 23:31   ` Ludovic Courtès

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=87vd0jwmff.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=bug-guile@gnu.org \
    --cc=idirectscm@aim.com \
    /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).