diff options
| author | Aki <please@ignore.pl> | 2022-08-11 23:00:34 +0200 |
|---|---|---|
| committer | Aki <please@ignore.pl> | 2022-08-11 23:00:34 +0200 |
| commit | a74cf471b8637a107b77a94717eba7c538b2964f (patch) | |
| tree | 7e7a7dc73a6a51045515c1b73b5c916cfbbe1995 /data/content/Screens/TacRefDlg.frm | |
| parent | ff972b194ff36252e9974327f66f05ea394fd704 (diff) | |
| download | starshatter-a74cf471b8637a107b77a94717eba7c538b2964f.zip starshatter-a74cf471b8637a107b77a94717eba7c538b2964f.tar.gz starshatter-a74cf471b8637a107b77a94717eba7c538b2964f.tar.bz2 | |
Code now consistently uses unique_ptr for arrays
Now, I realize this is a rather interesting choice. I want them to be consistent.
In case of extraction the array gets released as part of the legacy interface.
Because of this std::vector is out of question. All other cases could use it, but
they all have the same start and purpose. Only that one differs and I don't like
making it unique (pun intended).
Diffstat (limited to 'data/content/Screens/TacRefDlg.frm')
0 files changed, 0 insertions, 0 deletions