From: Keith Wright <kwright@gis.net>
Subject: Re: Ditching (debug-enable 'backwards) ?
Date: Mon, 28 Oct 2002 13:43:52 -0500 [thread overview]
Message-ID: <200210281843.g9SIhq401239@fcs9.free-comp-shop.com> (raw)
In-Reply-To: <E185rnl-0007Sa-00@giblet> (message from Thien-Thi Nguyen on Sun, 27 Oct 2002 10:06:17 -0800)
> From: Thien-Thi Nguyen <ttn@giblet.glug.org>
>
> From: Neil Jerram <neil@ossau.uklinux.net>
>
> Does anyone use (debug-enable 'backwards) and have a good
> reason for keeping it?
It looks like cruft to me.
> it is only pointless if you buy into a philosophy where you
> understand all points a priori.
I buy a philosophy that says you don't throw in things you don't
understand, but I don't buy Philosophy to the point that I try
to make a Zen koan out of every simple programming question.
> ... generally, orthogonal features can/should be documented in
> a likewise orthogonal style
Maybe the orthogonal way to do this would be to provide a way
to specify a script to be run on the output before displaying
it. The you can run your debug output through 'tac', 'grep',
'tee', or banner, at your option.
--
-- Keith Wright <kwright@free-comp-shop.com>
Programmer in Chief, Free Computer Shop <http://www.free-comp-shop.com>
--- Food, Shelter, Source code. ---
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2002-10-28 18:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-27 13:04 Ditching (debug-enable 'backwards) ? Neil Jerram
2002-10-27 18:06 ` Thien-Thi Nguyen
2002-10-27 19:00 ` Neil Jerram
2002-10-27 19:20 ` Thien-Thi Nguyen
2002-10-27 21:50 ` Neil Jerram
2002-10-28 18:43 ` Keith Wright [this message]
2002-11-03 17:41 ` Marius Vollmer
2002-11-04 20:01 ` Neil Jerram
2002-11-04 21:42 ` Marius Vollmer
2002-11-05 23:13 ` Neil Jerram
2002-11-06 12:50 ` Mikael Djurfeldt
2002-11-06 12:49 ` Mikael Djurfeldt
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=200210281843.g9SIhq401239@fcs9.free-comp-shop.com \
--to=kwright@gis.net \
/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).