Re: [selenium-dev] Selenium RC driver

2006-04-07 Thread Dan Fabulich
Good points there... Here's my two cents (and a bit). 0) Not explicitly highlighted, Selenium Core generates an XML file with a full description of its API; this is enough information to generate copious javadoc, ndoc, rdoc, pydoc, or POD perldoc. We should use it for something perl-ish, one wa

Re: Module requirements (was: Module::Build and installing in non-standardlocations)

2006-04-07 Thread Tels
Moin, On Friday 07 April 2006 02:55, Adam Kennedy wrote: > > I use 5.8.0 as minimum, but for unicode I think it should be 5.8.1 - > > but I am unsure. COuld you give a reason for why specifically 5.8.3? > > Actually, in consultation with Audrey and other $experts, > Perl::MinimumVersion applies a

Re: Module requirements

2006-04-07 Thread David Cantrell
chromatic wrote: On Thursday 06 April 2006 17:53, Adam Kennedy wrote: UNIVERSAL::isa/can when called as a function does a very specific thing, and one that is often misunderstood. ... and never correct, in the face of proxy objects, blessed objects, overloading, and ties. I disagree. In part

Re: Module requirements

2006-04-07 Thread Adam Kennedy
David Cantrell wrote: chromatic wrote: On Thursday 06 April 2006 17:53, Adam Kennedy wrote: UNIVERSAL::isa/can when called as a function does a very specific thing, and one that is often misunderstood. ... and never correct, in the face of proxy objects, blessed objects, overloading, and ties.

Re: Module requirements

2006-04-07 Thread demerphq
On 4/7/06, Adam Kennedy <[EMAIL PROTECTED]> wrote: > Just because I (repeatedly) attack chromatic over UNIVERSAL::isa/can > nobody should be under the impression that using the functions directly > is in any way a good thing. > > The only cases for which it's genuinely useful is asking "ignoring wh

Re: Module requirements

2006-04-07 Thread David Wright
On Fri, 7 Apr 2006, demerphq wrote: On 4/7/06, Adam Kennedy <[EMAIL PROTECTED]> wrote: Just because I (repeatedly) attack chromatic over UNIVERSAL::isa/can nobody should be under the impression that using the functions directly is in any way a good thing. The only cases for which it's genuine

Re: Module requirements

2006-04-07 Thread Ricardo SIGNES
* demerphq <[EMAIL PROTECTED]> [2006-04-07T08:32:35] > Actually afaik there is no good way to find out what dereferencing > operators an object supports. The best that I know of is reftype(), > but that only tells you the objects underlying intrinsic type, it > doesnt tell you if you can dereferenc

Re: Module requirements

2006-04-07 Thread demerphq
On 4/7/06, David Wright <[EMAIL PROTECTED]> wrote: > > On Fri, 7 Apr 2006, demerphq wrote: > > > On 4/7/06, Adam Kennedy <[EMAIL PROTECTED]> wrote: > >> Just because I (repeatedly) attack chromatic over UNIVERSAL::isa/can > >> nobody should be under the impression that using the functions directly

Re: Module requirements

2006-04-07 Thread demerphq
On 4/7/06, Ricardo SIGNES <[EMAIL PROTECTED]> wrote: > * demerphq <[EMAIL PROTECTED]> [2006-04-07T08:32:35] > > Actually afaik there is no good way to find out what dereferencing > > operators an object supports. The best that I know of is reftype(), > > but that only tells you the objects underlyi

Re: Module requirements

2006-04-07 Thread David Golden
David Wright wrote: Your $thingy could be a hashref, in which case $thingy->isa will die. The point of the discussion is that you should be checking if $thingy is blessed() first, as UNIVERSAL::isa breaks for objects that masquerade as other objects (e.g. via an adaptor pattern). I've been

Re: Module requirements

2006-04-07 Thread A. Pagaltzis
* Adam Kennedy <[EMAIL PROTECTED]> [2006-04-07 13:25]: > Just because I (repeatedly) attack chromatic over > UNIVERSAL::isa/can nobody should be under the impression that > using the functions directly is in any way a good thing. > > The only cases for which it's genuinely useful is asking > "igno

Re: Module requirements

2006-04-07 Thread chromatic
On Friday 07 April 2006 06:43, A. Pagaltzis wrote: > I still wonder what’s bad about using > > UNIVERSAL::can( $foo, "can" ) > > as a pre-Scalar::Util-compatible replacement of > > blessed( $foo ) > > that is, purely as a boolean test where only the truthness of the > return value is of in

Re: Module requirements

2006-04-07 Thread chromatic
On Friday 07 April 2006 05:32, demerphq wrote: > Actually afaik there is no good way to find out what dereferencing > operators an object supports. The best that I know of is reftype(), > but that only tells you the objects underlying intrinsic type, it > doesnt tell you if you can dereference the

Re: Module requirements

2006-04-07 Thread demerphq
On 4/7/06, chromatic <[EMAIL PROTECTED]> wrote: > On Friday 07 April 2006 05:32, demerphq wrote: > > > Actually afaik there is no good way to find out what dereferencing > > operators an object supports. The best that I know of is reftype(), > > but that only tells you the objects underlying intrin

Re: Module requirements

2006-04-07 Thread chromatic
On Friday 07 April 2006 10:48, demerphq wrote: > On 4/7/06, chromatic <[EMAIL PROTECTED]> wrote: > > eval { dereference_somehow( $thingie ) } > Sure, thats what i was saying elsewhere too. But I dont consider that > a reasonable solution. Consider if dreferencing it means executing it > and its