Question,
I am having a problem with some perl programs skipping records, it appears
to be a record locking issue. In other words program A locking a record
and
program B skipping the locked record.
I found the following code several layers deep in a call stack:
seek($file,$HDRSIZE+($blockno-1)*$IDXBSIZE,0) ||
die "Can't position index $file to block#$blockno: $!";
local($buff);
$IDXBSIZE == read($file,$buff,$IDXBSIZE) ||
die "Can't read a full Index block from $file: $!";
And then found an obscure reference in a manual, I know I actually read a
manual, that said || has higher order of operation than file functions and
that the "or" has a lower order of operation.
My question is am I interpreting the code above correctly to say, if
changed
from || to "or" will it cause a die to occur when a record lock is
encountered where it is currently skipping the locked record?
_______________________________________________
Perl-Unix-Users mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
