On Wed, Oct 04, 2006 at 12:01:22PM -0700, chromatic wrote:
> On Wednesday 04 October 2006 01:05, jesse wrote:
>
> > One of the things that many shops have defected from Perl to Java for
> > is the additional handcuffs that Java provides for less-than-experienced
> > developers. Giving me the power to control what my team, or folks using
> > my language variant, do could be a huge win.
>
> The point is that the person writing the program decides which handcuffs or
> costumes all of the code has to wear, not the person writing the libraries.
> If you want to set a policy for your organization, that's fine. It is just
> Not Okay for me or anyone to write a module right now that dictates exactly
> the strictness of every program written in the next twenty years that uses
> it.
So, you're in favor of Perl 6 not having a "use strict;"? Or are you in
favor of there being only one true strict?
Perhaps I'm misunderstanding what you mean by "person writing the
program" and "person writing the libraries." In fact, I've _gotta_
be. I'd like to be able to put my strictures in a library rather than
forcing them into the main body of a program. Are you saying
you don't want to let people do this?
Jesse
> -- c
>
--
