Path: utzoo!attcan!uunet!zephyr.ens.tek.com!tektronix!nosun!qiclab!m2xenix!puddle!f345.n109.z1.fidonet.org!Jason.Kankiewicz From: Jason.Kankiewicz@f345.n109.z1.fidonet.org (Jason Kankiewicz) Newsgroups: comp.lang.modula2 Subject: Multicompilers in Message-ID: <1273.26982CAD@puddle.fidonet.org> Date: 6 Jul 90 23:57:00 GMT Sender: ufgate@puddle.fidonet.org (newsout1.26) Organization: FidoNet node 1:109/345 - Hallucination, Fairfax VA Lines: 18 Why go through the trouble of calling separate compilers? It might be easier to have object code compatibility between several different compilers. With Benchmark, for example, assembly language can be used to write a module as long as you write a DEFINITION module for the assembly code, compile and link the assembly code and the run M2GenObm on it. Perhaps a similar method could be adopted for 'C' and other languages, then all you'd need is a M2GenOBM package that could incorporate the different object code standards. You wouldn't have to mess around with the compiler at all. The ideal situation would be to have several different language compilers which all produce the same kind of object code. I think Jensen & Partners Int. has done this with their TopSpeed line of compilers. -- uucp: uunet!m2xenix!puddle!109!345!Jason.Kankiewicz Internet: Jason.Kankiewicz@f345.n109.z1.fidonet.org