Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!ames!elroy!usc!hacgate!ashtate!dbase!awd
From: awd@dbase.UUCP (Alastair Dallas)
Newsgroups: comp.databases
Subject: Re: Linking MASM .OBJ file with PLINK86 (for Clipper A'87)
Summary: PUBLIC directive
Message-ID: <84@dbase.UUCP>
Date: 26 May 89 17:02:42 GMT
References: <1207@haydn.kulesat.uucp>
Organization: Ashton Tate Devlopment Center Glendale, Calif.
Lines: 21


I am sorry to post this, but we're having trouble with email (possibly
caused by my stupidity).  The subject line should warn away the uninterested.

When dBASE loads a binary file, it just does a JUMP to the start of the
file and starts executing, so the questioner's INT 17H program works.  In
a Clipper environment, however, the linker needs a label to identify where
to JUMP to.  Labels in a MASM program are not visible to the linker unless
they are first declared with the PUBLIC directive, as in:

	PUBLIC	Start


Start	Proc	Far
	....

Now, PLINK will know about Start and when Clipper calls Start, you'll get
to the same place.  Note, however, that parameter-passing conventions are
somewhat different.

/alastair/