RE: About Jade internals

Subject: RE: About Jade internals
From: "Didier PH Martin" <martind@xxxxxxxxxxxxx>
Date: Tue, 29 Dec 1998 19:57:30 -0500
Hi James

Yes indeed, you can consider the application as a module, do a CreateProcess
from the caller and communicate with it through a set of parameters. In
fact, Compilers like VC++ is doing that with the cl executable. What I want
is a module with a COM interface such that you can embed the interpreter as
an object for script languages like PerScript, PythonScript, JavaScript,
VBScript. For instance, within an ASP page, a developer can use the DSSSL
interpreter to process a document.

However, for the client side interpreter, I'll follow your advise by
changing the CreateProcess flag (Yes I got this annoying window when I did a
CreateProcess). Thanx, I just tested it and there is no more console window

Didier PH Martin

-----Original Message-----
From: owner-dssslist@xxxxxxxxxxxxxxxx
[mailto:owner-dssslist@xxxxxxxxxxxxxxxx]On Behalf Of James Clark
Sent: Monday, December 28, 1998 11:16 PM
To: dssslist@xxxxxxxxxxxxxxxx
Subject: Re: About Jade internals

Didier PH Martin wrote:
> Hi
> I am still strugling to transform Jade from a console EXE (on win32) into
> Dll. The goal is to be able to mount the dll and have a function to pass
> parameters like you actually do with the command line.

I still don't quite understand why you need to make it a DLL.

If you just want to avoid the console window popping up when you run in,
then you should just be able to use the DETACHED_PROCESS flag in
CreateProcess.  You can catch the errors using -f, or by redirecting
stderr to a pipe.


 DSSSList info and archive:

 DSSSList info and archive:

Current Thread