> fluid-let should *really* be called `now'), Agreed (about the `now' part) > Will this also apply to `use scope 'subs''? No. Only subs are affected, which is a clear and easy dividing line I believe. > I, for one, will *never* use such a construct. It provides the user > with the dangers of `no strict' combined with the illusion of safety > of `use strict'. Do you mean the whole thing, or just the `blocks' part? As I mentioned in response to Graham's email, the `blocks' scope might well be of little value, and might get the axe. Especially if you're used to using blocks for `now' scopes, then this proposal might actually be counterintuitive. -Nate
- RFC 64 (v1) New pragma 'scope' to change Perl's defa Perl6 RFC Librarian
- Re: RFC 64 (v1) New pragma 'scope' to change Perl... Graham Barr
- Re: RFC 64 (v1) New pragma 'scope' to change ... Nathan Wiger
- Re: RFC 64 (v1) New pragma 'scope' to cha... Ariel Scolnicov
- Re: RFC 64 (v1) New pragma 'scope' to... Nathan Wiger
- Re: RFC 64 (v1) New pragma 'scop... Ariel Scolnicov
- Re: RFC 64 (v1) New pragma '... John Porter
- Re: RFC 64 (v1) New pragma '... Nathan Wiger
- Re: RFC 64 (v1) New pragma 'scope' to cha... Bryan C . Warnock
- Re: RFC 64 (v1) New pragma 'scope' to... Nathan Wiger
- Re: RFC 64 (v1) New pragma 'scope' to change ... Michael Mathews
- Re: RFC 64 (v1) New pragma 'scope' to change ... Bart Lateur