On Dec 17, 2005, at 1:01 PM, Peter Schuller wrote: > What I *WOULD* expect in a decent environment is that concurrent > read-only access to things be safe unless explicitly documented to the > contrary. (I have ran into cases where this is not the case so I > realize > it is not a given in practice; but in an environment properly designed > for concurrency I think it should be (witness e.g. Java)).
Ah, but gethash is not read-only in SBCL, even if it is read-only from the point of view of the application. > In the JVM? I would be *massively* surprised if Araneida is unstable > because of problems in the JVM threading implementation. To the best > of my knowledge I have never ever ran into a threading related problem > in Java (other than bugs in application code). It all just works, > being designed for threading from the start... at least that is my > impression. Me too. It was the other backends I was wondering about. -- Brian Mastenbrook [EMAIL PROTECTED] http://brian.mastenbrook.net/ _______________________________________________ Gardeners mailing list [email protected] http://www.lispniks.com/mailman/listinfo/gardeners
