Make using new for allocating DF objects with vtables a compile-time error.
When done from plugins, it doesn't correctly initialize the vtable because of some weird things MSVC does, so the only safe way is to use df::allocate<df::foo>(). For consistency, it is also enforced for code in the main library. It reveals the issue in the digging invaders plugin, first found by warmist. This change is linked to a modification in df-structures codegen.develop
parent
98325757e2
commit
415cdad489
@ -0,0 +1 @@
|
||||
friend struct df::interfacest;
|
@ -1 +1 @@
|
||||
Subproject commit 9c280e13ab2e2421b8b8cab4a0c146fffc355a3c
|
||||
Subproject commit 1558b2373fcf8fa63928167e007a7f9a709888b6
|
Loading…
Reference in New Issue