in reply to Re: Ram file bug?
in thread Ram file bug?
Could you try again but undef $ram between the opens?
use strict; use warnings; my $ram; open RAM, '>', \$ram; seek RAM, 10, 0; print RAM ' '; warn length $ram;; undef $ram; open RAM, '>', \$ram; binmode RAM, ':raw' or warn $!; seek RAM, 10, 0; print RAM ' '; warn length $ram;; undef $ram; open RAM, '>:raw', \$ram; seek RAM, 10, 0; print RAM ' '; warn length $ram; warn `$^X -v`; __END__ C:\test>junk 11 at C:\test\junk.pl line 9. Use of uninitialized value in open at C:\test\junk.pl line 12. 11 at C:\test\junk.pl line 16. Use of uninitialized value in length at C:\test\junk.pl line 22. 0 at C:\test\junk.pl line 22. This is perl, v5.8.6 built for MSWin32-x86-multi-thread (with 3 registered patches, see perl -V for more detail) Copyright 1987-2004, Larry Wall Binary build 811 provided by ActiveState Corp. http://www.ActiveState. +com ActiveState is a division of Sophos. Built Dec 13 2004 09:52:01 Perl may be copied only under the terms of either the Artistic License + or the GNU General Public License, which may be found in the Perl 5 source ki +t. Complete documentation for Perl, including FAQ lists, should be found +on this system using `man perl' or `perldoc perl'. If you have access to + the Internet, point your browser at http://www.perl.org/, the Perl Home Pa +ge.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^3: Ram file bug?
by PodMaster (Abbot) on Feb 16, 2006 at 10:09 UTC |