This description isn't quite correct or complete. Hosts can distinguish
between memory that is executable and non-executable. In general it is not a
good idea in modern host to execute machine instructions from your data
space. It is much much easier to generate (compile/assemble/whatever) the
source language instructions into a standard and loadable module of
executable instructions (that is a shared library) and then to access that
shared library with cd. This gives the same power but in a much easier to
manage and standard manner.
The steps are:
1. create source statements in lanuage of your choice
2. compile source to object and link in a shared library
3. access your functions with cd
Note that you could manage the shared librarys as J nouns. You would write
them (perhaps to temp) before using cd to have the host load them for normal
access with cd.
----- Original Message -----
From: "Raul Miller" <[EMAIL PROTECTED]>
To: "Programming forum" <[email protected]>
Sent: Friday, July 13, 2007 10:27 PM
Subject: Re: [Jprogramming] J API
On 7/13/07, Don Guinn <[EMAIL PROTECTED]> wrote:
I thought that cd (15!:0) established a special environment to call a DLL
and could only interface to DLLs. And the DLL had to reside in a library
as
a file of type DLL. How would I use cd to call a program that resided in
a J
noun?
As I understand it:
[*] cd brings an image of the DLL into the current environment.
[2] j6.02 which should have the option of referring to pre-existing memory
(other than a DLL).
--
Raul
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
