The windows thread api is pretty similar to pthread and I still don’t get why
many open source projects don’t use a simple wrapper layer to abstract things.
(I’m not talking about pthreads32 BTW)
Here’s the old ofThread from OpenFrameworks that does exactly that:
As long as you’re doing the threading basics like running, joining, mutex, &
semaphores it’s not much code to provide access on both Windows & Unixes.
Perhaps this is something we could add to the Pure Data source code itself that
externals could then access. Basically just a layer with the usual callback
setting mechanism and a per-thread mutex. Maybe something like a “u_thread.c"
> On Sep 18, 2016, at 9:51 AM, pd-list-requ...@lists.iem.at wrote:
> From: Alexandre Torres Porres <por...@gmail.com <mailto:por...@gmail.com>>
> Subject: Re: [PD] [coll] bug
> Date: September 18, 2016 at 8:06:16 AM MDT
> To: Ivica Bukvic <i...@vt.edu <mailto:i...@vt.edu>>
> Cc: Pd-list <firstname.lastname@example.org <mailto:email@example.com>>
> 2016-09-18 4:43 GMT-03:00 Ivica Bukvic <i...@vt.edu <mailto:i...@vt.edu>>:
> Instead of outright removing the feature for all platforms when it works on 2
> out of 3 them, you could disable building it on Windows as it is very much
> useful on other platforms that support POSIX threads.
> In practice it still has it for the other platforms, cause deken still
> carries the previous packages. I agree though that it'd be better to just
> disable it for windows in the code, cause then the same package version could
> be updated for all platforms in deken, keeping them in sync with the same
> build version - and update the help file to say this was removed for the
> windows version because of a bug.
Pdfirstname.lastname@example.org mailing list
UNSUBSCRIBE and account-management ->