The suggestion to use the clipboard as an IPC method is a pretty sad commentary. The clipboard is a user interface concept, not another anonymous pipe you can open between two processes.

Scenario: The user starts your scripts, then goes on to do something entirely different, and on the first Ctrl+C, hoses your scripts. Of course, it's not obvious that the scripts have failed, and it probably won't be obvious why they failed. Unless the user does a Ctrl+V at some point, and chunks of perl object data are spewed into their document.

From an architectural point of view, it's merely a lack of thought about the data flow: other processes may poison or be poisoned by your use of that particular IPC channel. From a user design point of view, it's damaging the user interaction model by subverting the user's metaphor to grasp of what's going on in the computer.

Poking stuff into the clipboard is pretty cool: when the user directs the activity. Grabbing stuff from the clipboard is pretty cool: when the user directs the activity. The APIs were made quick and simple, to facilitate application designers who wanted to make their apps quick and simple.

--
[ e d @ h a l l e y . c c ]

In reply to Re: Re: Shared variables under win32? by halley
in thread Shared variables under win32? by xiper

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.