9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Rick Hohensee <humbubba@smarty.smart.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] usage of CPU server
Date: Thu,  2 Nov 2000 11:03:00 -0500	[thread overview]
Message-ID: <200011021603.LAA01579@smarty.smart.net> (raw)
In-Reply-To: <E13rHBq-000DqH-0V@anchor-post-31.mail.demon.net> from "nigel@9fs.org" at Nov 2, 0 10:02:54 am

> 
> >> Which bit of the Korn shell models the dependency graph?
> > > 
> > > 
> 
> > A dependancy graph is a tiny subset of what you can construct with -n and
> > friends, isn't it?
> 
> True, but it doesn't answer my question.  I asked "which bit of the
> Korn shell _models_ the dependency graph", not "which bits of the Korn
> shell can be assembled to create the same effect as the dependency
> graph in make".
> 
> I may as well have asked "which bits of the C language model the
> dependency graph", at which point your reply would have suggested that
> I should write a C program each time I want to assemble a kit of parts
> in the right order to create a whole.  Any language in which you can
> invoke other commands, test the relative age of files and do some
> filename manipulation is, according to your reply, better than make on
> the grounds that it is more general.
> 
> Now I'm not proposing that make is all we need; it's been superceded.
> However, I do suggest that the conciseness of a dependency graph
> notation is important.  There is plenty of evidence for this; the
> concept has been preserved in subsequent tools, IDEs etc..
> 
> So the question is, "which bit of the Korn shell _models_ the
> dependency graph?"
> 

You win your point, but mine is that modelling a dependancy graph within
the utility itself is not worth learning another "language". YMMV. I,
personnally, do things like convert the netpbm package to being make-less.

Rick Hohensee




  reply	other threads:[~2000-11-02 16:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-02 10:02 nigel
2000-11-02 16:03 ` Rick Hohensee [this message]
2000-11-02 16:27   ` Boyd Roberts
  -- strict thread matches above, loose matches on Subject: below --
2000-11-06 13:05 rob pike
2000-11-03 14:56 rob pike
2000-11-03 16:55 ` Elliott Hughes
2000-11-03 18:54   ` Boyd Roberts
2000-11-06  9:44 ` Douglas A. Gwyn
2000-11-02 18:02 rob pike
2000-11-03 14:22 ` Douglas A. Gwyn
2000-11-02 10:20 forsyth
2000-11-01  9:53 okamoto
2000-11-01 10:03 ` Lucio De Re
2000-11-01 14:46   ` Rick Hohensee
2000-11-01 15:19     ` nigel
2000-11-02  1:06       ` Rick Hohensee
2000-11-02  1:24         ` Boyd Roberts
2000-11-02  8:21           ` Rick Hohensee
2000-11-02 17:44           ` Douglas A. Gwyn
2000-11-02  7:55         ` Steve Kilbane
2000-11-02 11:25           ` Boyd Roberts
2000-11-01  9:08 forsyth
2000-11-01  7:27 okamoto
2000-11-01  8:21 ` Lucio De Re
2000-11-01  6:03 Russ Cox
2000-11-01  4:09 okamoto

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=200011021603.LAA01579@smarty.smart.net \
    --to=humbubba@smarty.smart.net \
    --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).