🚀 go-pugleaf

Christian Steinebach writes:
>
> I'll asks them whether they have an idea ( I really hope they have ),
> because using another SIMULA processor is not an option. I'm running
> LINUX on my PC and there is no other processor as far as I know.
> BTW It's not due to LINUX, the same error message appears on a SUN
> workstation with the SUN implementation of CIM.

 Two desperate suggestions:

 (1)  Since  we  know  that  cim  differs from the other compilers with
      respect to virtual parameter specification, look closely  at  the
      areas  affected  by this. It is just possible that where you have
      made changes because of this deviation from the standard there is
      some residual infelicity which  passes  the  Lund  compilers  but
      upsets cim.

 (2)  Have  you  tried  the age-old sledgehammer process of hacking out
      statement sequences incrementally until you  do  something  which
      removes   the  error?  Don't  take  out  declarations  and  block
      structure until that is all that is left!

 Don't expect the error message and its position to bear any
 relationship to what/where is the actual error. Compilers can be great
 liers especially when they're wrong!

 Just one more thought, at what stage in the compilation is this
 happening - during the translation to C or during the C compilation?
 Maybe your C compiler is faulty - the installation of cim on one of
 our machines revealed a weakness in that C compiler!

 Keep at it. We are all agog to hear the answer now!

 Hilsen....Ron