Re: ->isn't('UNIVERSAL') - stopping UNIVERSAL pollution?

Replies are listed 'Best First'.
Re^2: ->isn't('UNIVERSAL') - stopping UNIVERSAL pollution? by diotalevi (Canon) on Sep 05, 2006 at 23:35 UTC
Yeah... but I can't help wanting to at least ask if anyone has other ideas. ⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊	[reply]
Re^3: ->isn't('UNIVERSAL') - stopping UNIVERSAL pollution? by rir (Vicar) on Sep 06, 2006 at 03:27 UTC
I have not delved much into `Object::Deadly` and the pod seems a bit unclear. It seems that the intent is to mock up an object to be used in testing code that should not call any methods of the object, containers and such. If you want no methods to be called why use an object? `package Dont_touch; sub new { my $x; \$x; } 1;` [download] Since I don't know the underlying problem you're trying to solve, I'll shut my mouth now. Be well, rir	[reply] [d/l] [select]
Re^4: ->isn't('UNIVERSAL') - stopping UNIVERSAL pollution? by diotalevi (Canon) on Sep 06, 2006 at 12:57 UTC
The point is to have an object that isn't used in any way either as an object or as a value, boolean, string, or number. This is useful when testing things like Carp, Data::Dump::Streamer, etc. Anything which may find itself attempting to peek inside something that may be covered in arbitrary perl magic. This is an object which is covered in magic which complains loudly if you trigger any of it. ⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊	[reply]