Better Singleton classes C++: Revision history

28 December 2023

• curprev 17:5017:50, 28 December 2023‎ Jimg talk contribs‎ m 4,898 bytes +1,544‎ →‎Explanation
• curprev 00:1400:14, 28 December 2023‎ Jimg talk contribs‎ m 3,354 bytes +353‎ No edit summary

27 December 2023

• curprev 22:0522:05, 27 December 2023‎ Jimg talk contribs‎ m 3,001 bytes +84‎ No edit summary

16 May 2023

• curprev 21:1421:14, 16 May 2023‎ Jimg talk contribs‎ m 2,917 bytes −99‎ →‎What goes in the implementation
• curprev 21:1221:12, 16 May 2023‎ Jimg talk contribs‎ m 3,016 bytes +44‎ →‎What goes in the implementation

28 March 2023

• curprev 03:1403:14, 28 March 2023‎ Jimg talk contribs‎ m 2,972 bytes +43‎ →‎What goes in the header
• curprev 03:1303:13, 28 March 2023‎ Jimg talk contribs‎ m 2,929 bytes −47‎ →‎What goes in the implementation

16 February 2023

• curprev 05:1205:12, 16 February 2023‎ Jimg talk contribs‎ m 2,976 bytes +180‎ →‎What goes in the implementation
• curprev 05:0905:09, 16 February 2023‎ Jimg talk contribs‎ m 2,796 bytes +135‎ →‎What goes in the header

2 February 2023

• curprev 20:3820:38, 2 February 2023‎ Jimg talk contribs‎ m 2,661 bytes +6‎ No edit summary

• curprev 20:3420:34, 2 February 2023‎ Jimg talk contribs‎ 2,655 bytes +2,655‎ Created page with "We use lots of Singleton classes in the BES Framework. One issue with that pattern is that memory is usually not returned to the heap before the process exits, leaving tools like valgrind to report the memory as leaked. This is misleading and can be ignored, except that it's a great way to hide ''real'' leaks behind the noise in a sea of false positives. Here's a way around that using C++'s unquie_ptr. ## The basic plan I'll use a real example of this from the BES; the..."