On Fri, 2006-09-08 at 10:25 -0700, Erick Tryzelaar wrote: > skaller wrote: > > The result: Felix fibres can't deadlock. Finite streams > > are perfectly represented: if a thread tries to read > > past the end of a stream it just disappears, so the > > very question cannot arise. > > > > fyi, I had a case where I think I deadlocked the main thread > unexpectedly trying to read from a closed fibre, and it was GC'ed. I > think we ought to add some kind of option to warn/error out when this > happens.
Happens to me too .. in fact that was the indicator in the test case rt22a .. when i got deadlock/starvation the program terminated without any output. But I have no idea how to diagnose this and give a warning either at compile time or run time, because the 'unexpected' case and normal operation are distinguishable on in the programmers mind. There is one trick from embedded programming: watchdog. That puppy barks loudly if not fed a constant supply of bones. But I have no real idea how to implement that :) -- John Skaller <skaller at users dot sf dot net> Felix, successor to C++: http://felix.sf.net ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Felix-language mailing list Felix-language@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/felix-language
