[perl #31422] can't write open() wrapper without affecting how the FH is parsed

On Wed Dec 07 18:16:22 2011, jkeenan wrote:
> On Wed Dec 07 11:32:14 2011, andrew@pimlott.net wrote:
> 
> > 
> > Wow, I have no idea why I filed that bug (in 2004) either!  Your
> > follow-up is admirable. :-)
> > 
> 
> Well, I'm trying to make sure everyone who takes the time to file a bug
> report gets a response from a human in, say, eight years or less. ;-)
> 
> I'll take this ticket and hold it open for seven days in case you want
> to file an updated report.  Otherwise, we'll close it in a week's time.

I may have misunderstood the original report, but in any case there is a
bug here.

I think this report should stay open until we figure out some way to let
perl subs override open() with the same syntax, or decide that we’re not
going to.

   open(<FH>, $file); # syntax error
   myopen(<FH>, $file); # silently the wrong thing

   sub foo;
   open(foo, $file); # calls foo()
   myopen(foo, $file); # same as myopen("foo"...)

   sub foo() { 0 }
   open(foo, $file); # open(0, $file);
   myopen(foo, $file); # same (inconsistent with example above)


-- 

Father Chrysostomos

• Re: [perl #31422] can't write open() wrapper without affecting how the FH is parsed by Andrew Pimlott
• [perl #31422] can't write open() wrapper without affecting how the FH is parsed by James E Keenan via RT
• [perl #31422] can't write open() wrapper without affecting how the FH is parsed by Father Chrysostomos via RT
• [perl #31422] can't write open() wrapper without affecting how the FH is parsed by James E Keenan via RT
• [perl #31422] can't write open() wrapper without affecting how the FH is parsed by Father Chrysostomos via RT