| … | |
… | |
| 87 | |
87 | |
| 88 | =cut |
88 | =cut |
| 89 | |
89 | |
| 90 | package common::sense; |
90 | package common::sense; |
| 91 | |
91 | |
| 92 | our $VERSION = '0.03'; |
92 | our $VERSION = '0.04'; |
| 93 | |
93 | |
| 94 | sub import { |
94 | sub import { |
| 95 | # no warnings |
95 | # no warnings |
| 96 | ${^WARNING_BITS} ^= ${^WARNING_BITS}; |
96 | ${^WARNING_BITS} ^= ${^WARNING_BITS}; |
| 97 | |
97 | |
| … | |
… | |
| 106 | |
106 | |
| 107 | 1; |
107 | 1; |
| 108 | |
108 | |
| 109 | =back |
109 | =back |
| 110 | |
110 | |
| 111 | =head1 NO 'no common::sense' |
111 | =head1 THERE IS NO 'no common::sense'!!!! !!!! !! |
| 112 | |
112 | |
| 113 | This module doesn't offer an unimport. First of all, it wastes even more |
113 | This module doesn't offer an unimport. First of all, it wastes even more |
| 114 | memory, second, and more importantly, who with even a bit of common sense |
114 | memory, second, and more importantly, who with even a bit of common sense |
| 115 | would want no common sense? |
115 | would want no common sense? |
|
|
116 | |
|
|
117 | =head1 STABILITY AND FUTURE VERSIONS |
|
|
118 | |
|
|
119 | Future versions might change just about everything in this module. We |
|
|
120 | might test our modules and upload new ones working with newer versions of |
|
|
121 | this module, and leave you standing in the rain because we didn't tell |
|
|
122 | you. |
|
|
123 | |
|
|
124 | Most likely, we will pick a few useful warnings, instead of just disabling |
|
|
125 | all of them. And maybe we will load some nifty modules that try to emulate |
|
|
126 | C<say> or so with perls older than 5.10 (this module, of course, should |
|
|
127 | work with older perl versions - supporting 5.8 for example is just common |
|
|
128 | sense at this time. Maybe not in the future, but of course you can trust |
|
|
129 | our common sense). |
|
|
130 | |
|
|
131 | |
|
|
132 | =head1 WHAT OTHER PEOPLE HAVE TO SAY ABOUT THIS MODULE |
|
|
133 | |
|
|
134 | Pista Palo |
|
|
135 | |
|
|
136 | "Something in short supply these days..." |
|
|
137 | |
|
|
138 | Steffen Schwigon |
|
|
139 | |
|
|
140 | "This module is quite for sure *not* just a repetition of all the other |
|
|
141 | 'use strict, use warnings'-approaches, and it's also not the opposite. |
|
|
142 | [...] And for its chosen middle-way it's also not the worst name ever. |
|
|
143 | And everything is documented." |
|
|
144 | |
|
|
145 | BKB |
|
|
146 | |
|
|
147 | "[Deleted - thanks to Steffen Schwigon for pointing out this review was |
|
|
148 | in error.]" |
|
|
149 | |
|
|
150 | Somni |
|
|
151 | |
|
|
152 | "the arrogance of the guy" |
|
|
153 | "I swear he tacked somenoe else's name onto the module |
|
|
154 | just so he could use the royal 'we' in the documentation" |
|
|
155 | |
|
|
156 | dngor |
|
|
157 | |
|
|
158 | "Heh. '"<elmex at ta-sa.org>"' The quotes are semantic |
|
|
159 | distancing from that e-mail address." |
|
|
160 | |
|
|
161 | Jerad Pierce |
|
|
162 | |
|
|
163 | "Awful name (not a proper pragma), and the SYNOPSIS doesn't tell you |
|
|
164 | anything either. Nor is it clear what features have to do with "common |
|
|
165 | sense" or discipline." |
|
|
166 | |
|
|
167 | acme |
|
|
168 | |
|
|
169 | "THERE IS NO 'no common::sense'!!!! !!!! !!" |
|
|
170 | |
|
|
171 | crab |
|
|
172 | |
|
|
173 | "i wonder how it would be if joerg schilling wrote perl modules." |
| 116 | |
174 | |
| 117 | =head1 AUTHOR |
175 | =head1 AUTHOR |
| 118 | |
176 | |
| 119 | Marc Lehmann <schmorp@schmorp.de> |
177 | Marc Lehmann <schmorp@schmorp.de> |
| 120 | http://home.schmorp.de/ |
178 | http://home.schmorp.de/ |
