1N/Aprint "ok $N\n"; $N++;
1N/Aprint $o ?
"ok $N\n" :
"not ok $N\n";
1N/A# 12-20 same-length alterations 1N/A# 21-35 lengthening alterations 1N/A# 36-50 shortening alterations, including truncation 1N/A# (51-56) file with holes 1N/A# (57-59) zero out file 1N/A# (60-62) insert into the middle of an empty file 1N/A# (63-68) 20020326 You thought there would be a bug in STORE where if 1N/A# a cached record was false, STORE wouldn't see it at all. But you 1N/A# forgot that records always come back from the cache with the record 1N/A# separator attached, so they are unlikely to be false. The only 1N/A# really weird case is when the cached record is empty and the record 1N/A# (69-72) make sure that undefs are treated correctly---they should 1N/A# be converted to empty records, and should not raise any warnings. 1N/A# (Some of these failed in 0.90. The change to _fixrec fixed them.) 1N/A # If any of these raise warnings, we have a problem. 1N/A# (73-75) What if the user has tampered with $\ ? 1N/A{ { local $\ = "stop messing with the funny variables!"; 1N/A# my $open = open FH, "< $file"; 1N/A print "not ok $N\n# expected <$x>, got <$a>\n"; 1N/A ? "ok $N\n" : "not ok $N\n";