🚀 go-pugleaf

Recently, the occam compiler obstinately refused to compile the main 
routine of one of our programmes with the above error message. The manual
gives the wonderfully helpful hint that any of half a dozen or so resources
in the compiler could be exhausted, and suggests things like putting more
code into procedures, limiting the scope of variables, etc. Unfortunately,
doing any of these things would involve totally ripping up and reassembling
an already complicated piece of software -- after all, this is why we ran
into the problem in the first place.

Rather than touch a working thing, we ripped up our three transputer machines
to supply the host board (and thus the compiler) with an additional 2 MB
of memory, for a total of 4 MB. Lo and behold, said programme now compiles!

So far, so good. In the best of all worlds, however, we would like to have
some _simple_ means of determining exactly what resource the compiler runs
out of, before we turn to such desperate measures. In the absence of a more
detailed textual message, could my suspicion be correct that the strange 
numbers, e.g. `4315:0', which precede the error message, code in some way
for the information I want? And if so, could somebody be found with the
necessary table to decode them? And oh, what bliss, might said somebody
be able to supply that information to us? As e-mail, fax, even snail mail --
anything will be gratefully accepted!

-- Jan Vorbr"uggen, Institut f"ur Neuroinformatik,
                    Ruhr-Universit"t Bochum, FRG
   jan@pallas.neuroinformatik.rhuhr-uni-bochum.de
   
PS: Sorry about the somewhat sarcastic style, but this is the second time
in as many years I've spent days trying to find out what's wrong (three
compiler/code generation bugs last time), when just a little more information
would have spared all that agony. And I really like my transputers and their
occam, but sometimes they just get on my nerves :-)...