🚀 go-pugleaf

In article <1974@dasys1.UUCP> raylau@dasys1.UUCP (Raymond Lau) writes:
>Why can LSC use MPW Pascal code and not MPW C code?  Doesn't MPW Pascal
>and MPW C both compile to MPW's .o file format?  If so, I don't recall
>seeing a .o converter for LSC...though I know it exists for LSP.

	That was my mistake, I apologize. I mistyped. Here's the story:

	You can use MPW .O files (with some restrictions) in Lightspeed Pascal.

	You cannot use MPW .O files at all with LightspeedC.

	You cannot use LightspeedC Library files in Lightspeed Pascal.

	You cannot use Lightspeed Pascal Library files in LightspeedC.

>While on the subject of compatability, why didn't THINK make a utility to
>convert libraries, or even projects, between LSP and LSC?  (if not make

	Compatibility is planned between LSC and LSP, so you'll be able to
import or convert libraries between the two development systems.


>What about a LSC=>MPW .o converter too?  (and LSP too)

	No. Frankly, we're not interested in exporting to the MPW object
format.

>We have a .Rel=>LSC and .Rel=>LSP converter, what about the reverse?

	Ditto.

>Sometimes I find it helpful to have the ability to share object code w/others.

	Agreed.


	--Rich



**The opinions stated herein are my own opinions and do not necessarily
represent the policies or opinions of my employer (THINK Technologies, Inc).

* Richard M. Siegel | {decvax, ucbvax, sun}!harvard!endor!singer    *
* Customer Support  | singer@endor.harvard.edu			    *
* Symantec, THINK Technologies Division.  (No snappy quote)         *