On Friday 05 of November 2010 18:39:14 andrey mirtchovski wrote: > > To me, make is a tool for generating an acyclic, directed graph of > > dependencies between build steps from some explicit and some wildcard > > rules -- and then traversing it in a sensible order. How's that for > > daily use shell? > > your focus is too narrowed on building. a sequence of commands piping > output to each other is also a directed acyclic graph.
A bit in the style of plumber, one would have set of make-like rules defined in some $home/lib/mash, and mash would automagically apply them when target(s) match? Currently shell use consists of indicating data source and actions to be taken. With mash it would be more about indicating desired targets in the current context, to be created with mash rules in currenct context, right? On Friday 05 of November 2010 18:45:17 David Leimbach wrote: > The possibilities are finite! and so is the memory in a Turing machine... *mumbles something about turing tar-pit*
