| 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 <2018> 2019 2020 2021 2022 2023 2024 | Index | 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 <2018> 2019 2020 2021 2022 2023 2024 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: Issues with latest version of base-7.0 |
| From: | Marty Kraimer <[email protected]> |
| To: | [email protected] |
| Date: | Thu, 15 Nov 2018 14:54:57 -0500 |
On 11/14/18 10:17 PM, Johnson, Andrew N. via Core-talk wrote:
That is a really simple busy record and is most likely not appropriate for base. I suspect that there are applications that rely on semantics of the busy record from synapps.@Michael: call it experience of too many encounters with Murphy’s law... I don’t think it’s worth using a debugger, this is probably because of the slightly unusual behavior of the busy record, which I didn’t really think about or test with this change. The synapps busy record explicitly allows the database to determine when processing is complete and hence when to fire put-completion; you should probably take a look at the busy::process() routine to understand it. It has been suggested that we should add the busy record or something like it to base. Marty has a simple kind of busy record in the exampleCpp module.
Marty
I will look at Mark’s build issue when I get a chance, someone else here has also reported this, which is purely a warning message that I added but will probably disable for the final release. - Andrew