Hi,
If I'm writing apps to call functions from the newlisp.dll, are there some other functions I'll need to declare and implement, other than NewLispEvalStr, and a method for getting the string from the pointer?
I mean, we can evaluate one-line lisp statements like "( println 275 )", with NewLispEvalStr. But what about defines, and other more complicated statements? Do we just send an entire lisp program, as a single string with embedded carriage returns, to the NewLispEvalStr function?
Anything besides NewLispEvalString, for external access?
-
- Posts: 3
- Joined: Thu Aug 15, 2013 3:51 pm
Re: Anything besides NewLispEvalString, for external access?
Hello,
Regards
Yes, you can do this. You may also use load-command to load code into the dll.Do we just send an entire lisp program, as a single string with embedded carriage returns, to the NewLispEvalStr function?
Regards
Hans-Peter
-
- Posts: 3
- Joined: Thu Aug 15, 2013 3:51 pm
Re: Anything besides NewLispEvalString, for external access?
Ok thanks, HPW. I have see any references to load-command in the external interface docs, but can probably
just use a DLL viewer to determine the parameters.
just use a DLL viewer to determine the parameters.
-
- Posts: 3
- Joined: Thu Aug 15, 2013 3:51 pm
Re: Anything besides NewLispEvalString, for external access?
I don't see it documented anywhere. The only exports are
dllName, debugConsole, newlispEvalStr, newlispCallback, dllEvalStr, and WEP
Anyway, newlispEvalStr is good enough, thanks.
dllName, debugConsole, newlispEvalStr, newlispCallback, dllEvalStr, and WEP
Anyway, newlispEvalStr is good enough, thanks.