Am 26.01.2013 um 02:21 schrieb andy pugh: > On 26 January 2013 01:06, Michael Haberler <[email protected]> wrote: > >> I know barely anybody uses the threads module so that's likely safe but I'm >> raising it more to clarify semantics than to cry wolf. > > I use it very often (dozens of invocations a day), however I would > expect the threads to stop if I unloaded it.
then it warrants a closer look > In practice I generally exit HAL and see the threads stop. I have > never tried unloading "threads" in that setup you see threads stop because hal_lib is eventually unloaded; the sequence of events happening before that is what I would like to see spelled out to avoid surprises I would think barring a user-defined shutdown sequence it would be safest to immediately stop threads, and only then start unloading modules reaction to e-stop and abnormal termination of other parties, say milltask touches upon the same question note that the current 'solution' is to hope everything happens so fast the hardware doesnt have time enough to do something silly -m ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
