: Jeanna FOx wrote:
: > It also looks like some features are impossible to turn off -- like the
: > mandatory locking that jwz hates about Java. It's not safe to turn it
: > off, but it's not really safe with it on either. Some people would rather
: > loose the illusion of safety to get better performance.
: >
:
:
: Well, mandatory locking is something we should definetly NOT have in Perl6.
: Most of perl's code today is not threaded, and I believe much of it will
: continue to be this way. The pseudo-fork thread behaviour that is being
: proposed also makes this ok. Even if you have threads, you have to say
: explicitly if you want anythinig to be shared. And if you explicitly
: share something, then you should care the locks by yourself.
:
: At least, that's my opinion.
What would you say to a default behavior of locking - which may be explicity altered
with
the correct commands / arguments to fork() or Thread->new()? I kind of think it is
nice
not having to worry about locking semantics, but would like the ability to turn it all
off
if I want.
- tommy
