I don't see it documented anywhere. The only exports are
dllName, debugConsole, newlispEvalStr, newlispCallback, dllEvalStr, and WEP
Anyway, newlispEvalStr is good enough, thanks.
Search found 3 matches
- Thu Aug 15, 2013 10:48 pm
- Forum: newLISP and the O.S.
- Topic: Anything besides NewLispEvalString, for external access?
- Replies: 3
- Views: 4513
- Thu Aug 15, 2013 7:26 pm
- Forum: newLISP and the O.S.
- Topic: Anything besides NewLispEvalString, for external access?
- Replies: 3
- Views: 4513
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.
- Thu Aug 15, 2013 4:01 pm
- Forum: newLISP and the O.S.
- Topic: Anything besides NewLispEvalString, for external access?
- Replies: 3
- Views: 4513
Anything besides NewLispEvalString, for external access?
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 NewLispEva...