Petru Conduraru 4776bd7639 Atomic IFC file writes to prevent corruption on interrupted save (#4797) ...

file.write() streamed directly onto the target path, so a crash mid-write
left a truncated file with dangling STEP references. Serialize to a temp
file in the same directory, then atomically rename it onto the target.

- New IfcUtil::path::atomic_rename_file: std::rename on POSIX, MoveFileExW
  with MOVEFILE_REPLACE_EXISTING on Windows. Unlike rename_file it never
  unlinks the destination first, so there is no window where it goes missing.
- Fully in C++/swig (per aothms), so the FILE_NAME header is untouched: it
  comes from the model header, not the output path (verified empirically).
- Temp lives next to the target so the rename stays on one filesystem.
- Stream is closed before the rename (Windows cannot move an open file).
- On any write error the temp is removed and the original target is intact.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-07-07 14:22:44 +02:00

..

utils

ifcwrap: accept numpy scalars in aggregate type check #5873

2026-07-06 13:12:41 +02:00

CITATION.cff

Search replace 0.7.0 with 0.8.0

2024-06-27 11:49:12 +10:00

CMakeLists.txt

Option for ifcwrap cmake to run standalone #8165

2026-06-17 14:28:36 +02:00

IfcGeomWrapper.i

Small conv result number tweaks

2026-06-24 11:12:11 +02:00

IfcParseWrapper.i

Atomic IFC file writes to prevent corruption on interrupted save (#4797)

2026-07-07 14:22:44 +02:00

IfcPython.i

Minor changes to conversion result numbers

2026-06-23 20:25:57 +02:00