|
|
On Wed, 6 Jul 2022 at 16:41, Mohammed wrote:
>
> Wouldn’t using std::unique_ptr interfere with FLTK’s parent/child ownership system. If a unique_ptr fell out if scope it would call delete on the pointer and this might lead to issues.
>
Hi Mo,
Yes, that's a fair point.
I was kind of assuming the pointer was instantiated in some "global"
scope, but that may not be the case...
--
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/CAGFM6dZa4SVVbKWotknRM7gyRzzxOj2nH%3D8bjvOYTZg4djYWgA%40mail.gmail.com.
[ Direct Link to Message ] | |
|
| |