public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Stan Shebs <shebs@apple.com>
To: Eric McDonald <mcdonald@phy.cmich.edu>
Cc: mskala@ansuz.sooke.bc.ca, Tom Schaub <tom_and_sue_schaub@mac.com>,
	xconq7@sources.redhat.com
Subject: Re: does the tutorial lie?
Date: Fri, 28 May 2004 17:27:00 -0000	[thread overview]
Message-ID: <40B7764B.6050900@apple.com> (raw)
In-Reply-To: <1085709882.1485.553.camel@localhost.localdomain>

Eric McDonald wrote:

>On Thu, 2004-05-27 at 18:48, mskala@ansuz.sooke.bc.ca wrote:
>
>>I have not specifically tried the case you're talking about, but a couple
>>thoughts: First of all, the tutorial probably *does* lie.  So does most of
>>the rest of the documentation.  I've written things that the documentation
>>said would work, and had them not work, quite often.  You have to solve
>>these things by experiment, and preferably report it so the documentation
>>and/or code can be fixed.
>>
>
>I'm not going to sit here and get defensive about the manuals since I
>didn't write them, and have certainly been frustrated by them a number
>times as well.
>
>However, I am not sure that it is fitting to describe the manuals as
>"lying". I doubt that Stan wrote them with an intent to deceive.
>
My secret plot has been uncovered! People are supposed to get
discouraged and go play "Halo". Long arm of MS and all that... :-)

But seriously, people shouldn't be touching the sources without at
the same time checking that the manuals reflect reality. Better to
have the bugs and caveats documented than have the manual pretend
that some feature is fully functional.

The tutorial has a bit of a problem in that it doesn't consist of a
single game module that could be in the library and getting tested.
Perhaps a series of "checkpoints" of partial tutorial games for which
testing could be automated?

Stan

  parent reply	other threads:[~2004-05-28 17:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-27 23:55 Tom Schaub
2004-05-28  0:37 ` Stan Shebs
2004-05-28  0:47 ` mskala
2004-05-28  2:07   ` Eric McDonald
2004-05-28  6:45     ` Jim Kingdon
2004-05-28 16:46       ` Eric McDonald
2004-05-28 17:46       ` Stan Shebs
2004-05-28 17:27     ` Stan Shebs [this message]
2004-05-29  1:20       ` Eric McDonald

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

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

  git send-email \
    --in-reply-to=40B7764B.6050900@apple.com \
    --to=shebs@apple.com \
    --cc=mcdonald@phy.cmich.edu \
    --cc=mskala@ansuz.sooke.bc.ca \
    --cc=tom_and_sue_schaub@mac.com \
    --cc=xconq7@sources.redhat.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).