| 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 <2019> 2020 2021 2022 2023 2024 2025 | Index | 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 <2019> 2020 2021 2022 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: [Merge] ~epics-core/epics-base/+git/Com:thread-join into epics-base:7.0 |
| From: | "J. Lewis Muir via Core-talk" <[email protected]> |
| To: | [email protected] |
| Date: | Wed, 19 Jun 2019 15:06:22 -0000 |
> It's hard to use this correctly. Should you really implement a > joinWithTimeout() I think it should come with a big fat warning in the > documentation. I would certainly stay away from doing anything beyond calling > "exit" if join times out since I'm pretty sure I wouldn't get it right. I don't understand the concern here. If you're dealing with threads, you have to understand the memory model; that's a given. There are a practically infinite number of ways I can write wrong code with this API as well as the entire existing EPICS Base API. -- https://code.launchpad.net/~epics-core/epics-base/+git/Com/+merge/361379 Your team EPICS Core Developers is subscribed to branch epics-base:7.0.