🚀 go-pugleaf

   I use PolyMake, Multi-Edit and Stony Brook, and am thinking about
larding PVCS (like Polymake, a clone of UNIX make, this is a clone of
unix's source code control system) into the mix.  Together this works
out quite well.  I can run my make from inside Multi-Edit, Stony's
optimizing compiler is faster than any C compiler I ever saw, and I get
both quick results and compact code.
   Granted that this is a real kludge system taken overall, compared to
IDE's, the fact is that I come from the C world, have done UNIX develop-
ment, and am used to all of this.
   What I am getting is exceptional flexibility.  The editor I use is
100% configurable and programmable.  So is PolyMake.  And, for all
practical purposes, so is PVCS.  
   The net result is that I get things to run my way, as I find it
convenient, instead of the IDE developer's way, as he finds it 
convenient.  Polymake is entirely capable of putting new revisions of
a file into the archival system, drawing updates made in the meanwhile
out of the PVCS system, so when I move to PVCS, I'll have features which
are impossible for IDEs.
   The caveat, of course, is that this is a lot more work.  One has to
do the macros for the editor, munge up the polymake makefiles and so on.
   But I like doing it my way.  More, it doesn't change out from under
me with every new release, or every time a compiler vendor gets a briht
new idea.  My editor is bug-free, so is my current PolyMake and so on,
and the Stony Brook compiler won't be changing radically for a while.
So I'm quite stable.

--  
uucp: uunet!m2xenix!puddle!161!42!Frank.Warren
Internet: Frank.Warren@f42.n161.z1.fidonet.org