Re: interacting with an ACUCOBOL application

From: Paul Raulerson (paul_at_raulersons.com)
Date: 07/01/04

  • Next message: Robert Wagner: "Re: Testing and OO was Re: Is it possible to use the value of the PROGRAM ID within the source code?" 
    Date: 30 Jun 2004 16:04:38 -0700

    Well, I am not entirely clear what platform you are on, but have you
    looked into the platform's IPC capabilities?

    For example, under UNIX or (I think!) Windows, you should be able to
    build message queues and have a thread sitting there waiting on input
    to the queue.
    This is basically now 'event' notification works under Windows and X.
    There are several other possibilities- message queues, shared memory,
    semaphores, mutexs and so on.

    All of which, however, involve calling an operating system resource,
    which may or may not be easily done from modern AcuCobol. I tend to
    think
    it may be done with little effort, but I won't guarantee that.

    I can give you samples of how to do it under UNIX, but the samples are
    in C. :)

    -Paul

    mrissmann@yahoo.com (Mark_R) wrote in message news:<7a1f4dab.0406300656.fd4c35d@posting.google.com>...
    > Thanks for the suggestion but their current calls to my DLL are
    > unrelated to what I want to do here. When ever an certain event occurs
    > in my application I need to notify their application of the event and
    > pass some information over.
    >
    > I am not set on a using a DLL. Are there any other options? ActiveX?
    >
    > Thanks,
    >
    > -Markus
    >
    >
    > "JJ" <jj@nospam.com> wrote in message news:<R6qdnRNAQY1Tg3_dRVn-hg@comcast.com>...
    > > By "DLL messages", you mean sending messages to the Acucobol window - you
    > > could do that, but it's not the easiest or best way. (If I recall, Acucobol
    > > provides hooks where you can subclass the main window so you can intercept
    > > messages, but this requires writing some C code and relinking the runtime.)
    > >
    > > They can just pass you additional variables in their CALL of your DLL and
    > > your DLL can just put the values you want to pass back using the pointers to
    > > those variables. Or if they want, you can overwrite the values in the
    > > variables they are passing to you. Have them take a look at the docs on the
    > > CALL verb.

  • Next message: Robert Wagner: "Re: Testing and OO was Re: Is it possible to use the value of the PROGRAM ID within the source code?"

    Relevant Pages

    • Re: Linux, X, ld, gcc, linking, shared libraries and stuff
      ... "Cygwin"; This is a general project to make UNIX software run on Windows, ... a pretty simple idea...the Cygwin programs use the DLL as if it ...
      (alt.lang.asm)
    • Re: services for unix redistribution licence question
      ... IIRC, MSFU is free. ... area for either 'services for unix' or 'licensing'. ... Suppose I am porting to windows an application that currently uses Posix ... So if I make my product dependent on this DLL, ...
      (microsoft.public.win32.programmer.kernel)
    • Re: /MD vs /MT
      ... Do you mean inline member function being both in the DLL and the EXE, ... As you seem to be coming from a Unix background, ... while Windows relies on a more formal ...
      (microsoft.public.vc.mfc)
    • Re: Redirecting stderr
      ... programming newsgroup. ... There's no DLL support in the Unix version I use, ... If the code uses DLLs on Windows and shared libraries ...
      (comp.lang.c)
    • Re: .Net packaging/wrapper application?
      ... it just didn't work well in reality due to DLL ... Windows works is to look in the executable's directory for a needed DLL ... the way apps used to work when they developed Windows. ... Looks to me like Jim is looking for the .NET equivalent of compiling ...
      (microsoft.public.dotnet.framework.aspnet)