"SWM" == Steven W McDougall [EMAIL PROTECTED] writes:
Aha, I get it. -internals has been assuming that one _must_ specify
the sharing. You want it to be infered.
I think that's asking for too much DWIMery.
SWM Question: Can the interpreter determine when a variable becomes
SWM shared?
SWM
SWM Question: Can the interpreter determine when a variable becomes
SWM shared?
SWM Answer: No. Then neglecting to put a :shared attribute on a shared
SWM variable will crash the interpreter. This doesn't seem very Perlish.
Err, no. It won't crash the interpreter. It'll make the script
"SWM" == Steven W McDougall [EMAIL PROTECTED] writes:
SWM All I want the language to guarantee is internal thread-safety.
SWM Everything else is the user's problem.
Somehow I would have thought that goes without saying.
But I don't agree that all the rest is a user issue, is too
Single thingee access mediation, should be done automatically by perl.
The multi-thingee complex mediation should have the user step in, since
solving it (correctly and efficiently) is a complex problem.
I'm not sure we have a common understanding of the terms we are using.
Can you give some
I think we are talking about the same issues, but we can't seem to get
in sync on the terminology. I'm going to try to get off the
merry-go-round by recapitualting the two approaches.
RFC178
- globals are shared unless localized
- file-scoped lexicals are shared by all code in the file
-
