<![CDATA[Why QFile::close() call QIODevice::close() directly instead of call QFileDevice::close()]]>When I debugged the Qt source code, I found that QFile::close() call QIODevice::close() directly instead of call QFileDevice::close().
362a3988-2320-4564-8362-bc06e226175b-image.png
8fc61ed1-69e3-4582-abb2-187b99311791-image.png

]]>https://forum.qt.io/topic/145188/why-qfile-close-call-qiodevice-close-directly-instead-of-call-qfiledevice-closeRSS for NodeSun, 19 Apr 2026 10:43:45 GMTThu, 18 May 2023 02:43:35 GMT60<![CDATA[Reply to Why QFile::close() call QIODevice::close() directly instead of call QFileDevice::close() on Thu, 18 May 2023 05:48:21 GMT]]>@ChrisW67 I made a breakpoint at QFileDevice::close(),but the debugger never goes in.And only the QFileDevice::close() calls the QIODevice::close().How I found about this, because I found the file is still occupied after calls QFileDevice::close().But when not call close() explicitly and in QFile dctor call QFileDevice::close() implicit, the file will not be occupied.And this is only happend in my computer.
e1ccc069-709c-4429-88e3-8803e12d9f98-image.png

]]>https://forum.qt.io/post/758528https://forum.qt.io/post/758528Thu, 18 May 2023 05:48:21 GMT<![CDATA[Reply to Why QFile::close() call QIODevice::close() directly instead of call QFileDevice::close() on Thu, 18 May 2023 03:44:02 GMT]]>AFAICT QFile does not override QFileDevice::close() so QFile::close() is QFileDevice::close(). QFileDevice::close() calls QIODevice::close() after flush().

Perhaps you can identify where the QFile source code calls QIODevice::close() directly.

]]>https://forum.qt.io/post/758526https://forum.qt.io/post/758526Thu, 18 May 2023 03:44:02 GMT