avoid setting FILE lock count when not using flockfile
authorRich Felker <dalias@aerifal.cx>
Thu, 22 Sep 2011 01:30:45 +0000 (21:30 -0400)
committerRich Felker <dalias@aerifal.cx>
Thu, 22 Sep 2011 01:30:45 +0000 (21:30 -0400)
commitca52e347673126956a4f21247d8a551ea668f61f
treeca8a0e767640ca64fd91ab0d3edc75f24b269178
parent319df20bc9c20231d8efd810780c012cbdcfb109
avoid setting FILE lock count when not using flockfile

for now this is just a tiny optimization, but later if we support
cancellation from __stdio_read and __stdio_write, it will be necessary
for the recusrive lock count to be zero in order for these functions
to know they are responsible for unlocking the FILE on cancellation.
src/stdio/__lockfile.c