Gentlemen,

I've downloaded and installed cppscript for testing as a platform for a javascript program of mine.

I was in the middle of attempting to compile it before I began work on cleaning up and extending the code.

Unfortunately, there were a number of compiler errors that it threw which suggested that code for cppscript hasn't been updated for a very long time.

For starters, it doesn't refer to "DMC", it refers to "SC" which I've figured out is the older name for it.  I updated that part. Then I got errors about "dispex.h" not being found.  It's completely nonexistant in the new dmc includes folder.

So I found it on the 'net, resolved the errors I got from that, had to pull in a few more header files, but at this point it became error soup.

Alternatively, how can I get COM/ActiveX with DMDScript?

Dan wrote:
> I've downloaded and installed cppscript for testing as a platform
> for a javascript program of mine.
> 
> I was in the middle of attempting to compile it before I began work
> on cleaning up and extending the code.
> 
> Unfortunately, there were a number of compiler errors that it threw
> which suggested that code for cppscript hasn't been updated for a
> very long time.

You're right, it hasn't.

> For starters, it doesn't refer to "DMC", it refers to "SC" which
> I've figured out is the older name for it.  I updated that part.
> Then I got errors about "dispex.h" not being found.  It's completely
> nonexistant in the new dmc includes folder.

Sorry about that, it contains the COM and GUID declarations for dispatchex.

> So I found it on the 'net, resolved the errors I got from that, had
> to pull in a few more header files, but at this point it became
> error soup.
> 
> Alternatively, how can I get COM/ActiveX with DMDScript?

I don't understand the question.

I recently had a similar issue. My problem was that the Windows Include files that are included with DM are very old (Windows 95) and so don't include a lot of the COM declarations and so on.

I fixed it by copying all the files in the include directory for Visual Studio 6 into the DM Include directory.


"Walter Bright" <newshound2@digitalmars.com> wrote in message news:il15b8$nci$1@digitalmars.com...
> Dan wrote:
>> I've downloaded and installed cppscript for testing as a platform for a javascript program of mine.
>>
>> I was in the middle of attempting to compile it before I began work on cleaning up and extending the code.
>>
>> Unfortunately, there were a number of compiler errors that it threw which suggested that code for cppscript hasn't been updated for a very long time.
>
> You're right, it hasn't.
>
>> For starters, it doesn't refer to "DMC", it refers to "SC" which I've figured out is the older name for it.  I updated that part. Then I got errors about "dispex.h" not being found.  It's completely nonexistant in the new dmc includes folder.
>
> Sorry about that, it contains the COM and GUID declarations for dispatchex.
>
>> So I found it on the 'net, resolved the errors I got from that, had to pull in a few more header files, but at this point it became error soup.
>>
>> Alternatively, how can I get COM/ActiveX with DMDScript?
>
> I don't understand the question.

Nick Hofstetter wrote:
> I recently had a similar issue. My problem was that the Windows Include files that are included with DM are very old (Windows 95) and so don't include a lot of the COM declarations and so on.
> 
> I fixed it by copying all the files in the include directory for Visual Studio 6 into the DM Include directory.

That works, but it'd be better to just append the VS include path to the INCLUDE search path.

Its a bit more complex than that. There are a number of other header files that have changed that exisit in both locations so you really need all the 'later' Windows header files. Otherwise you don't have all the COM typedefs that are in older header files in the DM Include Directory. I tried just copying the 'Missing' files but things like 'windef.h' has changed.

But I agree my approach has probably broken things like 16 Bit Windows and DOS compiles, but everything I use complies correcly.

I also have a backup of the original Include directory so I can go back if ever necessary.


"Walter Bright" <newshound2@digitalmars.com> wrote in message news:il1t32$20vo$1@digitalmars.com...
> Nick Hofstetter wrote:
>> I recently had a similar issue. My problem was that the Windows Include files that are included with DM are very old (Windows 95) and so don't include a lot of the COM declarations and so on.
>>
>> I fixed it by copying all the files in the include directory for Visual Studio 6 into the DM Include directory.
>
> That works, but it'd be better to just append the VS include path to the INCLUDE search path.