Jump to content

Talk:Perl Object Environment

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Quinobi (talk | contribs) at 00:18, 16 July 2005 ({{to do}}). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

moved from Talk:POE 15:33, 12 July 2005 (UTC) Soft redirect to:Module:WikiProject banner/doc
This page is a soft redirect.

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]