COM. Questions and Bugs

Hi

I am trying to delve deeper into COM (don't ask why).

W.r.t. what I was doing yesterday I think I fixed a few things.

First of all: in order to properly use COM:MIDL, you need to be sure to 
have the environments variables PATH and INCLUDE properly set up.

The example is "processed" by MIDL as expected.

However.

1 - MIDL does not seem to produce any resulting files.  Is this correct?
2 - The COM browsers available in the Tools menu seem to work only on
     "internal data structures".  Is that the case?  If so, the code
     snippets are there to be copied and pasted into regular editor
     windows?

Now on to more substantial questions, which may be stupid, but I figured 
I may ask here instead of wasting time figuring it out.

How do you produce a COM object that can be called from C/C++?  Do you 
deliver a .DLL or an .EXE?  Any suggestions?

Finally the big one.

> 
> CL-USER 4 > (com:midl "ACTIVSCP.IDL")
> ;;; Processing ACTIVSCP.IDL
> ;;; Processing C:\Program Files\Microsoft Visual Studio\VC98\Include\ocidl.idl
> ;;; Processing C:\Program Files\Microsoft Visual Studio\VC98\Include\oleidl.idl
> ;;; Processing C:\Program Files\Microsoft Visual Studio\VC98\Include\objidl.idl
> ;;; Processing C:\Program Files\Microsoft Visual Studio\VC98\Include\unknwn.idl
> ;;; Processing C:\Program Files\Microsoft Visual Studio\VC98\Include\wtypes.idl
> ;;; Processing C:\Program Files\Microsoft Visual Studio\VC98\Include\oaidl.idl
> ;;; Processing C:\Program Files\Microsoft Visual Studio\VC98\Include\servprov.idl
> ;;; Processing C:\Program Files\Microsoft Visual Studio\VC98\Include\urlmon.idl
> ;;; Processing C:\Program Files\Microsoft Visual Studio\VC98\Include\msxml.idl
> 
> Error: [C:\Program Files\Microsoft Visual Studio\VC98\Include\ocidl.idl:1036]: Unexpected symbol "FontEvents"
> Skipping rest of statement.;; Enum tagSCRIPTSTATE as TAG-SCRIPTSTATE
> ;;   Enum Constant SCRIPTSTATE_UNINITIALIZED as SCRIPTSTATE_UNINITIALIZED
> ;;   Enum Constant SCRIPTSTATE_INITIALIZED as SCRIPTSTATE_INITIALIZED
> ;;   Enum Constant SCRIPTSTATE_STARTED as SCRIPTSTATE_STARTED
> ;;   Enum Constant SCRIPTSTATE_CONNECTED as SCRIPTSTATE_CONNECTED
> ;;   Enum Constant SCRIPTSTATE_DISCONNECTED as SCRIPTSTATE_DISCONNECTED
> ;;   Enum Constant SCRIPTSTATE_CLOSED as SCRIPTSTATE_CLOSED
> ;; Typedef SCRIPTSTATE as SCRIPTSTATE
> ;; Enum tagSCRIPTTHREADSTATE as TAG-SCRIPTTHREADSTATE
> ;;   Enum Constant SCRIPTTHREADSTATE_NOTINSCRIPT as SCRIPTTHREADSTATE_NOTINSCRIPT
> ;;   Enum Constant SCRIPTTHREADSTATE_RUNNING as SCRIPTTHREADSTATE_RUNNING
> ;; Typedef SCRIPTTHREADSTATE as SCRIPTTHREADSTATE
> ;; Typedef SCRIPTTHREADID as SCRIPTTHREADID
> 
> 
> **++++ Error in (SUBFUNCTION |COM Member : (I-ACTIVE-SCRIPT-SITE GET-ITEM-INFO)| (SUBFUNCTION (FLI:DEFINE-FOREIGN-FUNCTION |COM Member : (I-ACTIVE-SCRIPT-SITE GET-ITEM-INFO)|) (COM:COM-INTERFACE I-ACTIVE-SCRIPT-SITE))): 
>   Illegal foreign type I-TYPE-INFO.
> ; *** 1 error detected, no fasl file produced.
> NIL
> (((SUBFUNCTION |COM Member : (I-ACTIVE-SCRIPT-SITE GET-ITEM-INFO)| (SUBFUNCTION (FLI:DEFINE-FOREIGN-FUNCTION |COM Member : (I-ACTIVE-SCRIPT-SITE GET-ITEM-INFO)|) (COM:COM-INTERFACE I-ACTIVE-SCRIPT-SITE))) #<SIMPLE-ERROR 205FB02C>))
> T



I assume the above is a bug. (Actually more than one).
I really need this fixed.  Any idea about how to go ahead and do this?

Cheers

--
Marco Antoniotti

Re: COM. Questions and Bugs

Unable to parse email body. Email id is 898

Re: COM. Questions and Bugs

Thanks for the reply.

On Friday, Feb 28, 2003, at 13:17 America/New_York, Nick Levine wrote:

>
>    1 - MIDL does not seem to produce any resulting files.  Is this 
> correct?
>
> dunno
>
>    2 - The COM browsers available in the Tools menu seem to work only 
> on
> 	"internal data structures".  Is that the case?  If so, the code
> 	snippets are there to be copied and pasted into regular editor
> 	windows?
>
> The "COM Interface Browser" is fairly useful (although a navigation
> nightmare, plus a pain because you can't customize *package* in
> it)

Not good.  I need the package!


> . It tells you reliably what the interfaces you have on board. The
> code fragments are could be copied & customized, though I rarely
> bother (particularly because I use automation in preference to COM
> whenever I can).

I have not clear at all the difference between COM and automation in MS 
stuff.  I am pretty sure that the people at MS do not have it clear 
either. :)

>
>    Now on to more substantial questions, which may be stupid, but I
>    figured I may ask here instead of wasting time figuring it out.
>
>    How do you produce a COM object that can be called from C/C++?  Do
>    you deliver a .DLL or an .EXE?  Any suggestions?
>
> The application I'm working with more or less forces me to have lisp
> as the dll. I pass a pointer to Dispatch (ie pDispatch on the C++
> side, :pointer on the lisp side).

Ok.  I'll have to look into that.  Thanks.

>
>    Finally the big one...
>
> Send as much as you can to lisp-support. Backtraces, IDL files, etc.


The backtrace is exactly what you saw.  ACTIVESCP.IDL is a standard 
ActiveX IDL in MSVC.  It is the active scripting IDL.

Cheers

--
Marco Antoniotti
NYU Courant Bioinformatics Group		tel. +1 - 212 - 998 3488
715 Broadway 10th FL				fax. +1 - 212 - 998 3484
New York, NY, 10003, U.S.A.

Re: COM. Questions and Bugs

> 
> I have not clear at all the difference between COM and automation in MS 
> stuff.  I am pretty sure that the people at MS do not have it clear 
> either. :)
> 

I think it is like this:

COM is anything that supports IUnknown.

COM automation is anything that supports IDispatch.

OLE is automation + connection points + aggregation.

Re: COM. Questions and Bugs

On Friday, Feb 28, 2003, at 14:14 America/New_York, Joe Marshall wrote:

>>
>> I have not clear at all the difference between COM and automation in 
>> MS
>> stuff.  I am pretty sure that the people at MS do not have it clear
>> either. :)
>>
>
> I think it is like this:
>
> COM is anything that supports IUnknown.
>
> COM automation is anything that supports IDispatch.
>
> OLE is automation + connection points + aggregation.
>

Thanks.  I am not much into MS NewSpeak. :)

Cheers


--
Marco Antoniotti
NYU Courant Bioinformatics Group		tel. +1 - 212 - 998 3488
715 Broadway 10th FL				fax. +1 - 212 - 998 3484
New York, NY, 10003, U.S.A.

Re: COM. Questions and Bugs

I've been struggling with the COM functionality to get to the point 
where I can use it to drive Excel (I'm not sure if I'll ultimately use 
this route, but I'm at least trying to get it working), and have hit 
similar problems.  I think that the key part of the error message is:
>>(COM:COM-INTERFACE I-ACTIVE-SCRIPT-SITE))):    Illegal foreign type 
>>I-TYPE-INFO.
>> ; *** 1 error detected, no fasl file produced.

This keeps killing me too - some illegal foreign type which I have to 
spend inordinate amounts of time trying to track which type library it 
is defined in. In this case there appears to be a type library that 
includes ITypeInfo available from:
http://www.domaindlx.com/e_morcillo/scripts/type/default.asp

You can either define it to be part of a system using the 
:midl-type-library-file type (documented I believe) or use the 
undocumented COM:USE-TYPE-LIBRARY to load it.

I've also come across a definition for an IDL file for the ITypeInfo 
interface somewhere on the web - I'm sure Google will find it for you if 
you need it.

Hope this helps.

Regards
Guy.

In message <3E5FA2CD.4020004@cs.nyu.edu>, Marco Antoniotti 
<marcoxa@cs.nyu.edu> writes
>
>Hi
>
>I am trying to delve deeper into COM (don't ask why).
>
>W.r.t. what I was doing yesterday I think I fixed a few things.
>
>First of all: in order to properly use COM:MIDL, you need to be sure to 
>have the environments variables PATH and INCLUDE properly set up.
>
>The example is "processed" by MIDL as expected.
>
>However.
>
>1 - MIDL does not seem to produce any resulting files.  Is this correct?
>2 - The COM browsers available in the Tools menu seem to work only on
>    "internal data structures".  Is that the case?  If so, the code
>    snippets are there to be copied and pasted into regular editor
>    windows?
>
>Now on to more substantial questions, which may be stupid, but I 
>figured I may ask here instead of wasting time figuring it out.
>
>How do you produce a COM object that can be called from C/C++?  Do you 
>deliver a .DLL or an .EXE?  Any suggestions?
>
>Finally the big one.
>
>>  CL-USER 4 > (com:midl "ACTIVSCP.IDL")
>> ;;; Processing ACTIVSCP.IDL
>> ;;; Processing C:\Program Files\Microsoft Visual 
>>Studio\VC98\Include\ocidl.idl
>> ;;; Processing C:\Program Files\Microsoft Visual 
>>Studio\VC98\Include\oleidl.idl
>> ;;; Processing C:\Program Files\Microsoft Visual 
>>Studio\VC98\Include\objidl.idl
>> ;;; Processing C:\Program Files\Microsoft Visual 
>>Studio\VC98\Include\unknwn.idl
>> ;;; Processing C:\Program Files\Microsoft Visual 
>>Studio\VC98\Include\wtypes.idl
>> ;;; Processing C:\Program Files\Microsoft Visual 
>>Studio\VC98\Include\oaidl.idl
>> ;;; Processing C:\Program Files\Microsoft Visual 
>>Studio\VC98\Include\servprov.idl
>> ;;; Processing C:\Program Files\Microsoft Visual 
>>Studio\VC98\Include\urlmon.idl
>> ;;; Processing C:\Program Files\Microsoft Visual 
>>Studio\VC98\Include\msxml.idl
>>  Error: [C:\Program Files\Microsoft Visual 
>>Studio\VC98\Include\ocidl.idl:1036]: Unexpected symbol "FontEvents"
>> Skipping rest of statement.;; Enum tagSCRIPTSTATE as TAG-SCRIPTSTATE
>> ;;   Enum Constant SCRIPTSTATE_UNINITIALIZED as SCRIPTSTATE_UNINITIALIZED
>> ;;   Enum Constant SCRIPTSTATE_INITIALIZED as SCRIPTSTATE_INITIALIZED
>> ;;   Enum Constant SCRIPTSTATE_STARTED as SCRIPTSTATE_STARTED
>> ;;   Enum Constant SCRIPTSTATE_CONNECTED as SCRIPTSTATE_CONNECTED
>> ;;   Enum Constant SCRIPTSTATE_DISCONNECTED as SCRIPTSTATE_DISCONNECTED
>> ;;   Enum Constant SCRIPTSTATE_CLOSED as SCRIPTSTATE_CLOSED
>> ;; Typedef SCRIPTSTATE as SCRIPTSTATE
>> ;; Enum tagSCRIPTTHREADSTATE as TAG-SCRIPTTHREADSTATE
>> ;;   Enum Constant SCRIPTTHREADSTATE_NOTINSCRIPT as 
>>SCRIPTTHREADSTATE_NOTINSCRIPT
>> ;;   Enum Constant SCRIPTTHREADSTATE_RUNNING as SCRIPTTHREADSTATE_RUNNING
>> ;; Typedef SCRIPTTHREADSTATE as SCRIPTTHREADSTATE
>> ;; Typedef SCRIPTTHREADID as SCRIPTTHREADID
>>   **++++ Error in (SUBFUNCTION |COM Member : (I-ACTIVE-SCRIPT-SITE 
>>GET-ITEM-INFO)| (SUBFUNCTION (FLI:DEFINE-FOREIGN-FUNCTION |COM Member 
>>: (I-ACTIVE-SCRIPT-SITE GET-ITEM-INFO)|) (COM:COM-INTERFACE 
>>I-ACTIVE-SCRIPT-SITE))):    Illegal foreign type I-TYPE-INFO.
>> ; *** 1 error detected, no fasl file produced.
>> NIL
>> (((SUBFUNCTION |COM Member : (I-ACTIVE-SCRIPT-SITE GET-ITEM-INFO)| 
>>(SUBFUNCTION (FLI:DEFINE-FOREIGN-FUNCTION |COM Member : 
>>(I-ACTIVE-SCRIPT-SITE GET-ITEM-INFO)|) (COM:COM-INTERFACE 
>>I-ACTIVE-SCRIPT-SITE))) #<SIMPLE-ERROR 205FB02C>))
>> T
>
>
>
>I assume the above is a bug. (Actually more than one).
>I really need this fixed.  Any idea about how to go ahead and do this?
>
>Cheers
>
>--
>Marco Antoniotti
>
>
>

--

Re: COM. Questions and Bugs

On Friday, Feb 28, 2003, at 15:53 America/New_York, Guy Footring wrote:

> I've been struggling with the COM functionality to get to the point 
> where I can use it to drive Excel (I'm not sure if I'll ultimately use 
> this route, but I'm at least trying to get it working), and have hit 
> similar problems.  I think that the key part of the error message is:
>>> (COM:COM-INTERFACE I-ACTIVE-SCRIPT-SITE))):    Illegal foreign type 
>>> I-TYPE-INFO.
>>> ; *** 1 error detected, no fasl file produced.
>
> This keeps killing me too - some illegal foreign type which I have to 
> spend inordinate amounts of time trying to track which type library it 
> is defined in. In this case there appears to be a type library that 
> includes ITypeInfo available from:
> http://www.domaindlx.com/e_morcillo/scripts/type/default.asp

Sorry, but I do not understand the reference.  That is just a list of 
known interfaces.
The 'ITypeInfo' interface is defined in the standard file 'OAIDL.IDL' 
(which seems to be correctly processed by COM:MIDL.

>
> You can either define it to be part of a system using the 
> :midl-type-library-file type (documented I believe) or use the 
> undocumented COM:USE-TYPE-LIBRARY to load it.

I don't think this is going to work.  Eventually - AFAIU - you need to 
call COM:MIDL on a file containing the interface.  I can try to call 
COM:MIDL separately on 'OAIDL.IDL' to see whether I can load the 
'ITypeInfo' library beforehand.  Anyway, the 'FontEvents' error is 
still there.

>
> I've also come across a definition for an IDL file for the ITypeInfo 
> interface somewhere on the web - I'm sure Google will find it for you 
> if you need it.

You shouldn't be needing it.

>
> Hope this helps.
>

Well. It got me thinking.  Let's see how it works.

Cheers

Marco
--
Marco Antoniotti
NYU Courant Bioinformatics Group		tel. +1 - 212 - 998 3488
715 Broadway 10th FL				fax. +1 - 212 - 998 3484
New York, NY, 10003, U.S.A.

Re: COM. Questions and Bugs

In message <3BDB39E6-4B68-11D7-9090-000393A70920@cs.nyu.edu>, Marco 
Antoniotti <marcoxa@cs.nyu.edu> writes
>
>On Friday, Feb 28, 2003, at 15:53 America/New_York, Guy Footring wrote:
>
>> I've been struggling with the COM functionality to get to the point 
>>where I can use it to drive Excel (I'm not sure if I'll ultimately use 
>>this route, but I'm at least trying to get it working), and have hit 
>>similar problems.  I think that the key part of the error message is:
>>>> (COM:COM-INTERFACE I-ACTIVE-SCRIPT-SITE))):    Illegal foreign type 
>>>>I-TYPE-INFO.
>>>> ; *** 1 error detected, no fasl file produced.
>>
>> This keeps killing me too - some illegal foreign type which I have to 
>>spend inordinate amounts of time trying to track which type library it 
>>is defined in. In this case there appears to be a type library that 
>>includes ITypeInfo available from:
>> http://www.domaindlx.com/e_morcillo/scripts/type/default.asp
>
>Sorry, but I do not understand the reference.  That is just a list of 
>known interfaces.

At the bottom was the option to download the OLELIB.TLB file that could 
(presumably) be loaded with COM:USE-TYPE-LIBRARY.

>The 'ITypeInfo' interface is defined in the standard file 'OAIDL.IDL' 
>(which seems to be correctly processed by COM:MIDL.
>
>>
>> You can either define it to be part of a system using the
>> :midl-type-library-file type (documented I believe) or use the
>> undocumented COM:USE-TYPE-LIBRARY to load it.
>
>I don't think this is going to work.  Eventually - AFAIU - you need to 
>call COM:MIDL on a file containing the interface.

I'm only using COM:USE-TYPE-LIBRARY for what I'm doing, so using MIDL 
isn't necessarily required.  If I understand correctly (which could 
quite easily not be the case) the type library file is some kind of 
compiled IDL file.

>I can try to call COM:MIDL separately on 'OAIDL.IDL' to see whether I 
>can load the 'ITypeInfo' library beforehand.  Anyway, the 'FontEvents' 
>error is still there.
>

Looking in the ocidl.idl file the IFontsEventDisp interface doesn't 
follow the same pattern as the others in that the first statement isn't 
a typedef for IFontsEventDisp.  I've no idea whether this is a bug in 
ocidl.idl or simply something unusual that COM:MIDL is failing to deal 
with.  However, the FontsEvents error seems to have been recovered from, 
whereas the I-TYPE-INFO error was terminal.

>>
>> I've also come across a definition for an IDL file for the ITypeInfo 
>>interface somewhere on the web - I'm sure Google will find it for you 
>>you need it.
>
>You shouldn't be needing it.
>
>>
>> Hope this helps.
>>
>
>Well. It got me thinking.  Let's see how it works.
>
>Cheers
>
>Marco
>--
>Marco Antoniotti
>NYU Courant Bioinformatics Group               tel. +1 - 212 - 998 3488
>715 Broadway 10th FL                           fax. +1 - 212 - 998 3484
>New York, NY, 10003, U.S.A.
>

-- 
Regards
Guy.

Re: COM. Questions and Bugs

On Friday, Feb 28, 2003, at 17:32 America/New_York, Guy Footring wrote:

> In message <3BDB39E6-4B68-11D7-9090-000393A70920@cs.nyu.edu>, Marco 
> Antoniotti <marcoxa@cs.nyu.edu> writes
>>
>> On Friday, Feb 28, 2003, at 15:53 America/New_York, Guy Footring 
>> wrote:
>>
>>> I've been struggling with the COM functionality to get to the point 
>>> where I can use it to drive Excel (I'm not sure if I'll ultimately 
>>> use this route, but I'm at least trying to get it working), and have 
>>> hit similar problems.  I think that the key part of the error 
>>> message is:
>>>>> (COM:COM-INTERFACE I-ACTIVE-SCRIPT-SITE))):    Illegal foreign 
>>>>> type I-TYPE-INFO.
>>>>> ; *** 1 error detected, no fasl file produced.
>>>
>>> This keeps killing me too - some illegal foreign type which I have 
>>> to spend inordinate amounts of time trying to track which type 
>>> library it is defined in. In this case there appears to be a type 
>>> library that includes ITypeInfo available from:
>>> http://www.domaindlx.com/e_morcillo/scripts/type/default.asp
>>
>> Sorry, but I do not understand the reference.  That is just a list of 
>> known interfaces.
>
> At the bottom was the option to download the OLELIB.TLB file that 
> could (presumably) be loaded with COM:USE-TYPE-LIBRARY.


Ah.  Let me try it.

>
>> The 'ITypeInfo' interface is defined in the standard file 'OAIDL.IDL' 
>> (which seems to be correctly processed by COM:MIDL.
>>
>>>
>>> You can either define it to be part of a system using the
>>> :midl-type-library-file type (documented I believe) or use the
>>> undocumented COM:USE-TYPE-LIBRARY to load it.
>>
>> I don't think this is going to work.  Eventually - AFAIU - you need 
>> to call COM:MIDL on a file containing the interface.
>
> I'm only using COM:USE-TYPE-LIBRARY for what I'm doing, so using MIDL 
> isn't necessarily required.  If I understand correctly (which could 
> quite easily not be the case) the type library file is some kind of 
> compiled IDL file.
>
>> I can try to call COM:MIDL separately on 'OAIDL.IDL' to see whether I 
>> can load the 'ITypeInfo' library beforehand.  Anyway, the 
>> 'FontEvents' error is still there.
>>
>
> Looking in the ocidl.idl file the IFontsEventDisp interface doesn't 
> follow the same pattern as the others in that the first statement 
> isn't a typedef for IFontsEventDisp.  I've no idea whether this is a 
> bug in ocidl.idl or simply something unusual that COM:MIDL is failing 
> to deal with.  However, the FontsEvents error seems to have been 
> recovered from, whereas the I-TYPE-INFO error was terminal.

Ok.  You got further than I did on this one.

For the Lispworks people: it would be useful to know what exactly the 
MIDL file is doing.  I mean, at a high level, to understand its output.

Thanks

--
Marco Antoniotti
NYU Courant Bioinformatics Group		tel. +1 - 212 - 998 3488
715 Broadway 10th FL				fax. +1 - 212 - 998 3484
New York, NY, 10003, U.S.A.

Re: COM. Questions and Bugs

On Friday, Feb 28, 2003, at 17:37 America/New_York, Marco Antoniotti 
wrote:

>
> On Friday, Feb 28, 2003, at 17:32 America/New_York, Guy Footring wrote:
>
>> In message <3BDB39E6-4B68-11D7-9090-000393A70920@cs.nyu.edu>, Marco 
>> Antoniotti <marcoxa@cs.nyu.edu> writes
>>>
>>> On Friday, Feb 28, 2003, at 15:53 America/New_York, Guy Footring 
>>> wrote:
>>>
>>>> I've been struggling with the COM functionality to get to the point 
>>>> where I can use it to drive Excel (I'm not sure if I'll ultimately 
>>>> use this route, but I'm at least trying to get it working), and 
>>>> have hit similar problems.  I think that the key part of the error 
>>>> message is:
>>>>>> (COM:COM-INTERFACE I-ACTIVE-SCRIPT-SITE))):    Illegal foreign 
>>>>>> type I-TYPE-INFO.
>>>>>> ; *** 1 error detected, no fasl file produced.
>>>>
>>>> This keeps killing me too - some illegal foreign type which I have 
>>>> to spend inordinate amounts of time trying to track which type 
>>>> library it is defined in. In this case there appears to be a type 
>>>> library that includes ITypeInfo available from:
>>>> http://www.domaindlx.com/e_morcillo/scripts/type/default.asp
>>>
>>> Sorry, but I do not understand the reference.  That is just a list 
>>> of known interfaces.
>>
>> At the bottom was the option to download the OLELIB.TLB file that 
>> could (presumably) be loaded with COM:USE-TYPE-LIBRARY.
>

COM:USE-TYPE-LIBRARY is unbound and undefined in 4.2.7.

Now what?

--
Marco Antoniotti
NYU Courant Bioinformatics Group		tel. +1 - 212 - 998 3488
715 Broadway 10th FL				fax. +1 - 212 - 998 3484
New York, NY, 10003, U.S.A.

Re: COM. Questions and Bugs

Unable to parse email body. Email id is 907

Re: COM. Questions and Bugs

In message <EC832116-4B6E-11D7-9090-000393A70920@cs.nyu.edu>, Marco 
Antoniotti <marcoxa@cs.nyu.edu> writes
>
>On Friday, Feb 28, 2003, at 17:37 America/New_York, Marco Antoniotti 
>wrote:
>
>>
>> On Friday, Feb 28, 2003, at 17:32 America/New_York, Guy Footring wrote:
>>
>>> In message <3BDB39E6-4B68-11D7-9090-000393A70920@cs.nyu.edu>, Marco 
>>>Antoniotti <marcoxa@cs.nyu.edu> writes
>>>>
>>>> On Friday, Feb 28, 2003, at 15:53 America/New_York, Guy Footring 
>>>>wrote:
>>>>
>>>>> I've been struggling with the COM functionality to get to the 
>>>>>point where I can use it to drive Excel (I'm not sure if I'll 
>>>>>ultimately  use this route, but I'm at least trying to get it 
>>>>>working), and  have hit similar problems.  I think that the key 
>>>>>part of the error  message is:
>>>>>>> (COM:COM-INTERFACE I-ACTIVE-SCRIPT-SITE))):    Illegal foreign 
>>>>>>>type I-TYPE-INFO.
>>>>>>> ; *** 1 error detected, no fasl file produced.
>>>>>
>>>>> This keeps killing me too - some illegal foreign type which I have 
>>>>>to spend inordinate amounts of time trying to track which type 
>>>>>library it is defined in. In this case there appears to be a type 
>>>>>library that includes ITypeInfo available from:
>>>>> http://www.domaindlx.com/e_morcillo/scripts/type/default.asp
>>>>
>>>> Sorry, but I do not understand the reference.  That is just a list 
>>>>known interfaces.
>>>
>>> At the bottom was the option to download the OLELIB.TLB file that 
>>>could (presumably) be loaded with COM:USE-TYPE-LIBRARY.
>>
>
>COM:USE-TYPE-LIBRARY is unbound and undefined in 4.2.7.
>

It works for me in 4.2.7
I'm REQUIREing "com" and "automation".  Are you only REQUIREing "com"? 
Perhaps it is defined there.

Guy.

>Now what?
>
>--
>Marco Antoniotti
>NYU Courant Bioinformatics Group               tel. +1 - 212 - 998 3488
>715 Broadway 10th FL                           fax. +1 - 212 - 998 3484
>New York, NY, 10003, U.S.A.
>

--

Re: COM. Questions and Bugs

On Saturday, Mar 1, 2003, at 02:31 America/New_York, Guy Footring wrote:
>
> It works for me in 4.2.7
> I'm REQUIREing "com" and "automation".  Are you only REQUIREing "com"? 
> Perhaps it is defined there.
>

Thanks for the hint.  I was very stupid.

REQUIRing "automation" makes the

	(com:midl "ACTIVSCP.IDL")

call work. (Except for the FontEvents) problem.

I will keep you posted about my progress.

Cheers

--
Marco Antoniotti
NYU Courant Bioinformatics Group		tel. +1 - 212 - 998 3488
715 Broadway 10th FL				fax. +1 - 212 - 998 3484
New York, NY, 10003, U.S.A.