home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.forth
- Path: sparky!uunet!enterpoop.mit.edu!usc!sol.ctr.columbia.edu!venezia!penev
- From: penev@venezia (Penio Penev)
- Subject: Re: Documenting
- References: <4276.UUL1.3#5129@willett.pgh.pa.us>
- Sender: nobody@ctr.columbia.edu
- Organization: Rockefeller University
- Date: Wed, 27 Jan 1993 03:11:00 GMT
- X-Newsreader: TIN [version 1.1 PL6]
- Message-ID: <1993Jan27.031100.12971@sol.ctr.columbia.edu>
- Reply-To: penev@venezia.rockefeller.edu
- X-Posted-From: venezia.rockefeller.edu
- NNTP-Posting-Host: sol.ctr.columbia.edu
- Lines: 28
-
- ForthNet articles from GEnie (ForthNet@willett.pgh.pa.us) wrote:
- : Category 3, Topic 3
- : Message 99 Tue Jan 26, 1993
- : G.LEFAVE [Gene] at 06:02 EST
- :
- : > Building a nucleus to use a particular shared library or a combination
- : > of them is no more than 5 min work in the beginning of the development
- : > of Your application. This ideology should work quite well with all
- : > breeds of Unix which support shared libraries.
- :
- : If there was ever a topic for Forth Dimensions this has to be it! Will this
- : work with DOS?
-
- I don't know whether DOS uses shared libraries. I know Linux uses
- them. The necessity to connect to shared libraries never arose to me
- while I was working under DOS. The used mechanism there was to connect
- through user-installed interrups. I DOS uses shared libraries though,
- I think, that one can connect to it. The trick, which I use, is to
- write an empty C program, which declares enough space for FORTH's
- nucleus (I put this in the .data segment) and for the dictionary later
- ( in the .bss segment). If You are willing enough You could use the
- malloc function of C for space management.
-
- I implemented this under IRIX (a Unix flavour). I'll have to implement
- it for Linux soon, because I'm buying a PC. If anybody is willing to
- try for smth. else, I can provide my experience along with some code.
-
- -- Penio.
-