Re: [perl #125569] [PATCH] modify behavior of SCALAR in*{"_<$filename"} dbg glob for mem saving

* Elizabeth Mattijsen <liz@dijkmat.nl> [2016-01-29 12:55]:
> * On 29 Jan 2016, at 12:37, bulk88 via RT <perlbug-followup@perl.org> wrote:
> > Who has a perl source code file, name "1"? Yes, no .pl, no .pm. Just
> > a file called "1" on disk.
>
> FWIW, I do. And “2”, and “3”. Simple stuff I use during testing.
> Throwawayable for sure.

Yeah. It wouldn’t do to restrict what filenames could be stored. But
bulk88 actually kinda missed his own point here – whether anybody has
files named like that is besides the point. This is what he wrote just
before the part you quoted:

* bulk88 via RT <perlbug-followup@perl.org> [2016-01-29 12:40]:
> Filenames are always strings, not IVs. Storing a filename as
> a "dualvar" is insane.

So filenames that are just numbers could still be stored, it would just
not be possible to convert them to actual integers. Which I agree with
him is… well, maybe not insane outright, but certainly a silly thing to
spend resources on.

• [perl #125569] [PATCH] modify behavior of SCALAR in *{"_<$filename"}dbg glob for mem saving by bulk88 via RT
• Re: [perl #125569] [PATCH] modify behavior of SCALAR in*{"_<$filename"} dbg glob for mem saving by Ricardo Signes
• [perl #125569] [PATCH] modify behavior of SCALAR in *{"_<$filename"}dbg glob for mem saving by Tony Cook via RT
• [perl #125569] [PATCH] modify behavior of SCALAR in *{"_<$filename"}dbg glob for mem saving by bulk88 via RT
• Re: [perl #125569] [PATCH] modify behavior of SCALAR in*{"_<$filename"} dbg glob for mem saving by Elizabeth Mattijsen
• Re: [perl #125569] [PATCH] modify behavior of SCALAR in*{"_<$filename"} dbg glob for mem saving by Aristotle Pagaltzis