🚀 go-pugleaf

In article <JAN.92Aug12103429@pallas.neuroinformatik.ruhr-uni-bochum.de> jan@pallas.neuroinformatik.ruhr-uni-bochum.de (Jan Vorbrueggen) writes:
>
>Actually, I think the control of disk files is what the TDS does best. When
>we converted our main Occam programme from TDS to the toolset, a collegue
>spent several days of labour (as in GULAG) to produce the makefile. And every
>time you add a file to the thing, you start thinking about the dependencies
>and what you have to add to the makefile. None of that with the TDS. On the
>other hand, developing with multiple authors is that much harder, and some
>sensible versioning system would have enhanced the value of the TDS much.

Am I missing the point here, but, there is a utility in the latest version
of the Occam toolset (also in the latest version of the c toolset and if
I remember, is also in the D705 product)---ANYWAY: the utility is called
imakef and builds a makefile (complete with all necessary dependencies).  It
does this by backtracking from the desired .btl/.b8h/etc. to all .occ/.pgm 
files.   Although you do *have* to use standard file extensions so that
imakef can work.  The make program is *not* supplied with the toolset, but
we were able to obtain one from an ftp site.  At this most, most of us here
now rely on this feature - and new user/students come quickly up to speed as
well

Brian d'Auriol

A