http://www.perlmonks.org?node_id=329202


in reply to Re: Re: Inline::C *back* into Perl
in thread Inline::C *back* into Perl

You consider that making it easy?

Here are a few issues to think through.

  1. Any decent GUI program needs to handle interrupts well. It was doing X, the user decides not to and interrupts it. The API that you are describing offers no good way to pass interrupts along.
  2. The system that you describe doesn't seem to have a lot of debugging hooks when things go wrong.
  3. A huge problem with Expect is that unusual, unexpected or unanticipated input causes programs to diverge. When the GUI and internal program diverge on what they think is being displayed, you can readily get into deadlocks.
  4. What you are describing sounds like a lot of overhead at all ends.
If you want a text-based cross-language approach to GUI developlment, I would suggest using httpd instead. No, it is not perfect. But it does a good job of addressing most of the above problems and furthermore has the virtue of already being built.