Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbnewse!cwpjr
From: cwpjr@cbnewse.att.com (clyde.w.jr.phillips)
Newsgroups: comp.lang.forth
Subject: Re: Linking, Modules, and Overlays
Summary: Welcome aboard.
Message-ID: <1991Feb27.152553.24657@cbnewse.att.com>
Date: 27 Feb 91 15:25:53 GMT
References: <2420.UUL1.3#5129@willett.pgh.pa.us>
Distribution: na
Organization: AT&T Bell Laboratories
Lines: 21

In article <2420.UUL1.3#5129@willett.pgh.pa.us>, ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie) writes:
> 
>  I'm primarily a C coder, just starting to learn forth.  I'm hoping

Once again welcome. How did you learn to take FORTH seriously? This is not
a trick question. I'm curious because primarily C coders can easily
beleive there is no need for anything but C, ie a bit dogmatic.
I have C folks who are interested in FORTH, so any comments would be welcome.

As for your question, you are in the right place and we are cuurently
discussing the "call interface" issue. I'll let the working practitioners
of this art respond...

>  that I'm understanding defining words correctly.  I'm attempting to
>  build a Desqview Interface to F83.  Some of the direct call to the
>  Desqview API use the same registers.   Are the following two screens
...to this also-------------------------------------------------^^^^^^
>  a proper use of defining words?
> 
>  \  Direct call interface, no return values          91-02-23 sms
Clyde