| From | Sent On | Attachments |
|---|---|---|
| Jesse Vincent | May 7, 2011 9:23 am | |
| Tom Christiansen | May 7, 2011 9:26 am | |
| Karl Williamson | May 7, 2011 9:35 am | |
| H.Merijn Brand | May 7, 2011 9:47 am | |
| Leon Timmermans | May 7, 2011 10:11 am | |
| Tom Christiansen | May 7, 2011 10:17 am | |
| chromatic | May 7, 2011 10:37 am | |
| Jesse Vincent | May 7, 2011 11:09 am | |
| Leon Timmermans | May 7, 2011 11:17 am | |
| Jesse Vincent | May 7, 2011 11:37 am | |
| Abigail | May 7, 2011 3:09 pm | |
| Abigail | May 7, 2011 3:14 pm | |
| Tom Christiansen | May 7, 2011 3:16 pm | |
| David Golden | May 7, 2011 6:19 pm | |
| Aristotle Pagaltzis | May 7, 2011 6:34 pm | |
| Steffen Mueller | May 8, 2011 10:52 am | |
| Rafael Garcia-Suarez | May 8, 2011 11:20 am | |
| Father Chrysostomos | May 8, 2011 2:19 pm | |
| Tom Christiansen | May 8, 2011 2:27 pm | |
| David Golden | May 8, 2011 8:32 pm | |
| Rafael Garcia-Suarez | May 9, 2011 12:10 am | |
| Jan Dubois | May 9, 2011 1:45 am | |
| David Golden | May 9, 2011 2:49 am | |
| Ed Avis | May 10, 2011 8:50 am | |
| Zsbán Ambrus | May 10, 2011 9:08 am | |
| Aristotle Pagaltzis | May 10, 2011 2:52 pm | |
| Jesse Vincent | May 11, 2011 3:28 pm | |
| Jesse Vincent | May 11, 2011 3:30 pm | |
| Joshua ben Jore | May 15, 2011 11:48 am | |
| Jesse Vincent | May 15, 2011 11:54 am |
| Subject: | Re: v5.16 and warning by default [was: Re: Why no used once warning on lexicals?] | |
|---|---|---|
| From: | Joshua ben Jore (twi...@gmail.com) | |
| Date: | May 15, 2011 11:48:46 am | |
| List: | org.perl.perl5-porters | |
On Sat, May 7, 2011 at 10:18 AM, Tom Christiansen <tchr...@perl.com> wrote:
Leon Timmermans <faw...@gmail.com> wrote on Sat, 07 May 2011 19:12:20 +0200:
Actually, I'd personally prefer the warnings to be promoted to exceptions. Warnings are often far too easily missed. That said, some warnings can be a bit confusing then set to fatal.
The problem with that is that compile-time warnings promoted into exceptions don't work. They kill the compiler, which means you never learn what the real problem was.
I find this interesting. I ran into a code base which had evolved without strict.pm. To ever be able to sanely add strict.pm, it'd have to be implementable as a warning. I've been of the opinion that everything strict.pm does ought to be able to considered just warnings that have been promoted to 'FATAL'.
Josh





