Properly handle method_named ops
authorVincent Pit <vince@profvince.com>
Thu, 19 Aug 2010 14:22:05 +0000 (16:22 +0200)
committerVincent Pit <vince@profvince.com>
Thu, 19 Aug 2010 14:22:58 +0000 (16:22 +0200)
commit109b4f5ea15c640ab7a2eec463cc354754cc5d91
treeb2f36139955a58d9e6c204a0f0ad57ecfbd69ecb
parentc2ba713757508f871a8d84014fcf26cd791dc265
Properly handle method_named ops

They are directly generated (i.e. without being mutated from a method op)
for use foo/no foo. This should solve the random failures of t/30-scope.t.
MANIFEST
indirect.xs
t/47-stress-use.t [new file with mode: 0644]