On Sat, Feb 12, 2005 at 05:24:04PM -0600, Jonathan Scott Duff wrote: > > >Because of this, I'd suggest that autothreading of user-defined routines > > >not be the default, but rather enabled via a pragma of some sort (or, of > > >course, via an "autothreaded" trait). For the built-in routines this > > >isn't a worry as we get to design them appropriately. > > > > This seems to be needlessly optimizing for the rare case. And needlessly > > restrictive. > > Perhaps. I'm not so sure it's the rare case that programmers aren't > prepared to deal with implicit parallelization. :-) > > Part of the appeal of perl is that people of all skill/knowledge levels > can jump in and start doing useful work. Autothreading by default has > the potential to force people to be aware of junctions before they are > ready to understand them.
Autothreading, even if enabled by default, doesn't happen until a junction is created and used somewhere. Thus the only time our hypothetical new programmer would be forced to become aware of junctions (without himself/herself having created a junction) is when he/she calls some routine that chooses to generate and return a junction on its own. That isn't likely to happen often. Pm
