From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: the licence
Date: Fri, 23 Feb 1996 03:25:17 -0500 [thread overview]
Message-ID: <19960223082517.5m9GzDtNjh0F-jbCjYSw29FwQarezeSyu1CEYVfVxx8@z> (raw)
>>If you can rewrite a code generator in less time than you can throw
>>out a set of makefiles for a smallish source tree and rewrite some
>>simple ones to replace them, then there's something wrong, and it's
>>not with Perl.
funnily enough, it turns out that i can really can write and debug
code generators in much less time than it takes me to work out what
a config script (not for Perl) is doing to do to a collection of Makefiles, and
what the Makefiles will do when i run them, given that the output
of `make -n' is a cascade of shell `if' statements
(and this is on Unix, not Plan 9).
next reply other threads:[~1996-02-23 8:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-02-23 8:25 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-02-23 17:06 pete.fenelon
1996-02-23 15:28 Arnold
1996-02-23 14:05 Boyd
1996-02-23 14:00 Boyd
1996-02-23 9:06 forsyth
1996-02-23 8:41 forsyth
1996-02-23 8:17 Nigel
1996-02-23 4:45 Luther
1996-02-23 4:18 Greg
1996-02-23 2:31 Luther
1996-02-23 1:20 Paul
1996-02-23 0:08 forsyth
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=19960223082517.5m9GzDtNjh0F-jbCjYSw29FwQarezeSyu1CEYVfVxx8@z \
--to=forsyth@plan9.cs.york.ac.uk \
/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).