On 09 Aug 2000 09:40:29 +0100, Piers Cawley wrote: >> Now, what you can do, is stat() on the filehandle, and pick out the >> device ID and the inode number. That combination is unique for each >> file. > >And what happens when its a tied filehandle? Or are we going to >require that the tying class provides a STRINGIFY method as well? Required? No. The default for stringify is the familiar "Foo::Bar=HASH(0x8a6f088)" format. If you're too lazy to implement it, you get the same as you have now. It will be used mostly for debugging purposes, anyway. If in some way open() is used internally with a real file handle, the data coming from there could be incorporated in your "stringified" output. -- Bart.
- Re: Treating filehandles like strings Jon Ericson
- Re: Treating filehandles like strings Nathan Wiger
- Re: Treating filehandles like strings Bart Lateur
- Re: Treating filehandles like strings Jonathan Scott Duff
- Re: Treating filehandles like strings Jon Ericson
- Re: Treating filehandles like strings Hildo Biersma
- Re: Treating filehandles like st... Jon Ericson
- Re: Treating filehandles like strings Piers Cawley
- Re: Treating filehandles like strings Bart Lateur
- Re: Treating filehandles like strings Bennett Todd
- Re: Treating filehandles like strings Bart Lateur
- Re: Treating filehandles like strings Jonathan Scott Duff
- Re: Treating filehandles like st... Bart Lateur
- Re: Treating filehandles lik... Jonathan Scott Duff
- Fw: Treating filehandles like strings Michael Mathews