I'm about to turn threaded builds back on in my smoke configurations now that they (hopefully) don't hang any more on Win32, but the smokes really take too long then because there are too many configuration combinations. So I'm considering removing PERL_COPY_ON_WRITE from the configurations. Will anyone miss this? If keeping it would be useful then I can set up a smoke to exercise it instead of threads, say, once a week. --Thread Next