| Ani-_ | GumbyBRAIN: DST |
| GumbyBRAIN | Ehm secure up the dst stuff done last week... A few systems here and hate it that way. Might spur a large buffer. |
| Glanzmann | perl -wlne '/([a-z])/ and print $1' bbl |
| action | dazjorz goes upstairs to check the server |
| dazjorz | goes upstairs to check the server it's rebooting for teh debian |
| Ani-_ | You don't need reboots. |
| action | CPAN upload: OpenOffice-OODoc-2.034 by JMGDOC |
| CPAN | upload: OpenOffice-OODoc-2.034 by JMGDOC |
| Elly | is use warnings FATAL => qw(all) too strict for production code? |
| Randal | yes |
| Elly | yes? |
| Randal | yes |
| Elly | why? |
| Ani-_ | undefined values |
| Elly | undefined values shouldn't happen |
| Randal | because warnings change over time |
| Elly | if they do, I have a logic error |
| Randal | qw(! , #) formerly didn't warn now it does perfectly valid code can throw warnings |
| Elly | why does that warn? |
| Randal | warnings should NEVER be on in production |
| Elly | wait, what? |
| Ani-_ | eval: use warnings; qw(! , #); |
| buubot | Ani-_: Possible attempt to separate words with commas at eval line 1. Useless use of a constant in void context at eval line 1. Useless use of a constant in void context at eval line 1. # |
| Ani-_ | That's why |
| Elly | what happened to "always use strict and warnings" |
| Randal | warnings are meant for DEVELOPERS to figure out why their code isn't working |
| Elly | oh |
| Randal | always use warnings in *development* |
| Elly | but I am developing :P |
| Ani-_ | Elly: see how it says use warnings. See how it does not say: use fatal warnings |
| Randal | .. <Elly> is use warnings FATAL => qw(all) too strict for production code? that was your question that's why I said "yes" |
| Elly | okay I'm using fatal warnings while I develop anyway |
| dazjorz | eeeek |
| Randal | warnings are hints that your code *might* be bad |
| dazjorz | can't just switch from netbsd to debian |