any limitations on variable types when usind an in process dll?

Hello,
I want to write some subroutines in VB and then have a lisp routine use those subroutines.
I will need to pass those subroutines parameters and get info back.
I know that you cannot use a list as a parameter, you would have to format things in a safearray.

What other variable types are not compatible between lisp and activex functions?
If its just arrays, I can deal with that.
The reason I want to use lisp is that it is great at getting info from a user when picks are involved.
Things like grread and grdraw are just not available in vb or vba so I want to make hybrids.
Also I am finding the LDT API has bugs when called from lisp, the objects are not released correctly.
I have struggled with this for two years and Peter Funk is aware of it, Civil3D is where the programmers are though.
So I want to have a vb function do the API interaction and hopefully that will smoothe things out.
Lots of other reasons too for doing hybrids...

I am truing to decide if there would be any serious roadblocks though for sending and getting data from activex type
functions.
thanks

James Maeding
jmaeding at hunsaker dot com
Civil Engineer/Programmer

 

James,

With respect to LDT and LISP are you importing the type libraries and
accessing functions from there? I know with ADT it's the only way to work
with AEC objects: access to ALL the properties, reactors fire when supposed
to, ObjectDBX works better, etc.

Sorry, can't help you with the VB stuff, but I know I have NO problems
working with ADT objects in this way.

jb

 

thx for the comments.
My situation will probably be simpler since I will be making the dll's.


"James Buzbee" <>
|>James,
|>
|>With respect to LDT and LISP are you importing the type libraries and
|>accessing functions from there? I know with ADT it's the only way to work
|>with AEC objects: access to ALL the properties, reactors fire when supposed
|>to, ObjectDBX works better, etc.
|>
|>Sorry, can't help you with the VB stuff, but I know I have NO problems
|>working with ADT objects in this way.
|>
|>jb
|>

James Maeding
jmaeding at hunsaker dot com
Civil Engineer/Programmer

 

I just read the reply my NG prog posted and have no idea what the heck happened.
What I said made no sense and I think I was trying to post to some other thread....
I know this thread is dead but for future readers, I dont want to look totally stupid and arrogant by posting something
that looked irrelevent, like I knew what I was taling about...

The answer is yes, I will be referencing the type libraries when making the dll. I will not have to do it like you say
exactly but its the same idea. Sorry for the wierd previous response...

"James Buzbee" <>
|>James,
|>
|>With respect to LDT and LISP are you importing the type libraries and
|>accessing functions from there? I know with ADT it's the only way to work
|>with AEC objects: access to ALL the properties, reactors fire when supposed
|>to, ObjectDBX works better, etc.
|>
|>Sorry, can't help you with the VB stuff, but I know I have NO problems
|>working with ADT objects in this way.
|>
|>jb
|>

James Maeding
jmaeding at hunsaker dot com
Civil Engineer/Programmer

 

Too late! ;-)

jb