9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Harri Haataja <harriha@mail.student.oulu.fi>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] debugging p9p threads question
Date: Sun,  7 Aug 2005 02:48:45 +0300	[thread overview]
Message-ID: <20050806234844.GC2988@harriha-dsl.oulu.fi> (raw)
In-Reply-To: <20050803072008.GG9518@server4.lensbuddy.com>

On Wed, Aug 03, 2005 at 08:20:08AM +0100, Uriel wrote:
> 
> The most effective debugging tool is still careful thought, coupled with
> judiciously placed print statements.
> 
>     -- Brian W. Kernighan, in the paper Unix for Beginners (1979)

At http://www.haskell.org/hawiki/QuotesPage:

seen on news://comp.lang.functional

> By the way seriously: how do you debug Haskell programs?

Mostly seriously: I don't. If the programme doesn't work the
way I intended it, I rewrite bits in a simpler fashion until
I understand it well enough and it works. For the sort of
programme you were asking for, breaking things up until they
are small enough that one can understand the individual
parts completely (as I did in the solution I posted) and
then composing them together really is the best approach.

If you need to debug a programme that simple, what it's
telling you is that you've written it the wrong way!

--
Jón Fairbairn


-- 
For indoor or outdoor use only
		-- Warning on a Xmas lights set


  parent reply	other threads:[~2005-08-06 23:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-02 22:42 Ronald G. Minnich
2005-08-02 22:48 ` Russ Cox
2005-08-02 23:00   ` Ronald G. Minnich
2005-08-02 23:36     ` Charles Forsyth
2005-08-03  7:20     ` Uriel
2005-08-03 10:40       ` Russ Cox
2005-08-03 12:12         ` Ronald G. Minnich
2005-08-06 23:48       ` Harri Haataja [this message]
2005-08-09 14:48         ` Gorka guardiola
2005-08-03  0:12 YAMANASHI Takeshi
2005-08-03  0:31 ` Skip Tavakkolian
2005-08-03  5:49   ` LiteStar numnums
2005-08-03  6:56   ` Tim Newsham

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=20050806234844.GC2988@harriha-dsl.oulu.fi \
    --to=harriha@mail.student.oulu.fi \
    --cc=9fans@cse.psu.edu \
    /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 NNTP newsgroup(s).