Talk:Perl Object Environment

To-do list for Perl Object Environment: edit · history · watch · refresh · Updated 2005-07-16

Talk:Perl Object Environment

Documentation of History Merge from Talk:POE into Talk:Perl Object Environment

Untitled

History merge of Talk:POE into Talk:Perl Object Environment done by Jerzy•t, 10 September 2005:

  • 22:39, 10 September 2005 Jerzy restored "Talk:Perl Object Environment"
  • 22:37, 10 September 2005 Jerzy m (Talk:POE has been moved to Talk:Perl Object Environment.)
  • 22:36, 10 September 2005 Jerzy deleted "Talk:Perl Object Environment" (Momentary to merge talk history after C&P merge from Talk:POE)

The remainder of this super-section documents the original histories.

Pre-Merge History under Title Talk:Perl Object Environment

  • 00:18, 16 July 2005 Quinobi ({{to do}})
  • 15:33, 12 July 2005 Quinobi (discussion from POE stub ... fixing to become a redirect to here.)
  • 15:26, 12 July 2005 Quinobi (WikiProjectNotice|Computer_science)

Pre-Merge History under Title Talk:POE

  • 22:37, 10 September 2005 Jerzy m (Talk:POE has been moved to Talk:Perl Object Environment.)
  • 15:34, 12 July 2005 Quinobi (Discussion moved to Talk:Perl Object Environment)
  • 08:13, 10 July 2005 Quinobi (... or something like that.thing to remember is perl is called a 'glue' language. I read that somewhere and it stuck)
  • 05:19, 17 May 2005 69.3.238.199 (removed my outdated opinion)
  • 07:57, 13 July 2004 67.101.149.198 (Mach microkernel???!)
  • 08:34, 19 March 2004 Will m (Edgar Allen Poe --> Edgar Allan Poe)
  • 23:11, 3 March 2004 XTaran (POE == adhocracy? I don't believe...)

Post-Move Discussion

The move mentioned immediately below

  • was a cut&paste move
  • included only material below here (but not all of it, since more has been added since).

--Jerzy•t 05:29, 11 September 2005 (UTC)Reply
moved from Talk:POE 15:33, 12 July 2005 (UTC)

Wonder, what

adhocracy ad-hoc'-ra-cy: Any form of organization that cuts across normal bureaucratic lines to capture opportunities, solve problems, and get results.

has to do with POE. The text does describe adhocracy and seems nothing to do with POE respective explaining what connects adhocracy with POE. Google has very few hits for "POE adhocracy" and usually they were book lists, containing at least one book of Edgar Allan Poe. I'll insert a description for POE and remove the current one for now. --XTaran 23:11, 3 Mar 2004 (UTC)

POE has a large following and like perl's motto says - "There's more than one way to do it." The Panel Of Experts, Primary Objective for Exploitation is to PrOvidE a safe lexically scoped Pristine Object Enclosure where blessed objects are free to romp and play like Primates On Elephants. I may be have Plenty Of Errors in my thinking but from what I've read in the documents, the evironmnet containes very dedicated handlers for specific processes, working in a very lean and tight server/client relationship where unexpected states are simply irrelevant because they are kept outside of the scope of each running poe through class exclusion... or something like that.
As for adhocracy, POE is like a network of processes that are somewhat self-hosted, abstract and informal, thus lend easily to ad hoc structures versus bottom up or top down like you'ld see in more formal networks. The thing to remember is perl is called a 'glue' language. I read that somewhere and it stuck. Quinobi 08:13, 10 July 2005 (UTC)Reply

What licence?

Latest comment: 19 years ago2 comments2 people in discussion

POE is probably free software, but I can't find the licence on the website. If someone knows for sure, can they note in the article that it is free software and what free software licence it uses? Ta. Gronky 23:52, 9 February 2007 (UTC)Reply

FOSS fanboyism, anyone? I've never seen a Perl module on CPAN that wasn't licensed the same as Perl itself. From http://search.cpan.org/~rcaputo/POE-0.9999/lib/POE.pm#AUTHORS_&_COPYRIGHT :
Except where otherwise noted, POE is Copyright 1998-2005 Rocco Caputo. All rights reserved. POE is free software; you may redistribute it and/or modify it under the same terms as Perl itself.
Larry Wall made an "artistic license" for Perl, but it's also released under the GPL, which is more robust. Tafinucane 18:00, 30 July 2007 (UTC)Reply
Latest comment: 17 years ago1 comment1 person in discussion

The image Image:Programming-republic-of-perl.png is used in this article under a claim of fair use, but it does not have an adequate explanation for why it meets the requirements for such images when used here. In particular, for each page the image is used on, it must have an explanation linking to that page which explains why it needs to be used on that page. Please check

  • That there is a non-free use rationale on the image's description page for the use in this article.
  • That this article is linked to from the image description page.

This is an automated notice by FairuseBot. For assistance on the image use policy, see Wikipedia:Media copyright questions. --23:54, 1 October 2008 (UTC)Reply

Content Disclaimer

Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.

  1. The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
  2. There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
  3. It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
  4. Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
  5. Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.