in reply to Sharing variables between applications

I'm confused by your description. I understand that you have two perl apps that run independently -- Do they both have GUIs? Your opening sentence also mentions a "compiled exe" (so I gather you are using ms-windows) -- How does this relate to the two perl apps? Do you generally (or sometimes) use each app independently, or are they always used in combination (because they are interrelated / interdependent)?

Here's a suggestion, based on a wild guess about what you are trying to describe. If app2 will continue to be useful on its own as a GUI, and a particular subroutine in app2 does what is needed in app1, then the simplest thing would be to isolate that subroutine as a module (along with anything else it needs to do its job), so that both app1 and app2 can use it, without getting bogged down in IPC issues (which tend to be a little trickier when applied to scripts that have GUIs).

  • Comment on Re: Sharing variables between applications

Replies are listed 'Best First'.
Re^2: Sharing variables between applications
by fanticla (Scribe) on Jul 04, 2010 at 17:00 UTC

    Thank you all for your suggestions

    @graff: the two (GUI) applications are two different piece of software doing two different things. They are generally used indipendently from each other. As things grow up, I notice they could share some data. Example: App1 is an interface to a SQlite database. Just managing various data. App2 elaborates statistical alalysis from texts. Just thought it nice, if I could "bring togheter" the two things: For example doing some statistical data in App2 starting from a query result in App1.

    By now I think the easiest thing to do is use a exchange-database or something like that, as suggested in a reply.

[reply]

In Section Seekers of Perl Wisdom