Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!maytag!watstat!dmurdoch
From: dmurdoch@watstat.waterloo.edu (Duncan Murdoch)
Newsgroups: comp.lang.pascal
Subject: Re: TP .obj?
Message-ID: <1071@maytag.waterloo.edu>
Date: 1 Jan 90 23:21:26 GMT
References: <1490006@hpmcaa.mcm.hp.com> <1867@bucket.UUCP>
Sender: daemon@maytag.waterloo.edu
Reply-To: dmurdoch@watstat.waterloo.edu (Duncan Murdoch)
Organization: U. of Waterloo, Ontario
Lines: 19

In article <1867@bucket.UUCP> leonard@bucket.UUCP (Leonard Erickson) writes:
>
>On the other hand, you can link in
>any .obj file just by doing $L name.obj. You do have to follow a few
>simple rules about segment names, but that's it.

There are very strong restrictions on the .obj files, that essentially limit
you to linking assembly code, not any high level language.  
  - you can have only one code segment
  - you can have only one data segment, and it can't have initialized data
  - any external references have to be resolved in the TP code, not in other
    .OBJ files or .LIBs.

I think it would be a good idea to complain about this to Borland.  I've heard
the same restrictions apply to Microsoft's QuickPascal, but I can't imagine that
Microsoft will keep them for long - their big fat MS Pascal can link to 
any other Microsoft language.  

Duncan Murdoch