> IME, I find it more dangerous to do behind-the-scenes hand holding than > to simply teach them the hows and whys of the "right way." Exactly. > The key word above is "encourage". You're not really encouraging > anything - you're now having the language mandate particular constructs, > without the added benefit of teaching people why these constructs are > important. This too. People should know: 1. What they're doing 2. Why they're doing it Not: 1. How to turn annoying messages off -Nate
- RFC 16 (v1) Keep default Perl free of constraints su Perl6 RFC Librarian
- Re: RFC 16 (v1) Keep default Perl free of constra... Nathan Wiger
- Re: RFC 16 (v1) Keep default Perl free of con... Simon Cozens
- Re: RFC 16 (v1) Keep default Perl free of... Bryan C . Warnock
- Re: RFC 16 (v1) Keep default Perl fre... Jeremy Howard
- Re: RFC 16 (v1) Keep default Per... Bryan C . Warnock
- Re: RFC 16 (v1) Keep default... Nathan Wiger
- Re: RFC 16 (v1) Keep default Perl free of con... J. David Blackstone
- Re: RFC 16 (v1) Keep default Perl free of... Johan Vromans
- Re: RFC 16 (v1) Keep default Perl free of constra... J. David Blackstone
- Re: RFC 16 (v1) Keep default Perl free of con... Peter Scott
- Re: RFC 16 (v1) Keep default Perl free of con... Johan Vromans
- Re: RFC 16 (v1) Keep default Perl free of... Peter Scott
- Re: RFC 16 (v1) Keep default Perl fre... Jonathan Scott Duff
- Re: RFC 16 (v1) Keep default Perl fre... Chaim Frenkel