r42585 - in /branches/upstream/libcommon-sense-perl/current: COPYING Changes LICENSE MANIFEST META.yml README sense.pm

ryan52-guest at users.alioth.debian.org ryan52-guest at users.alioth.debian.org
Sun Aug 23 20:59:52 UTC 2009


Author: ryan52-guest
Date: Sun Aug 23 20:59:46 2009
New Revision: 42585

URL: http://svn.debian.org/wsvn/pkg-perl/?sc=1&rev=42585
Log:
[svn-upgrade] Integrating new upstream version, libcommon-sense-perl (1.0)

Added:
    branches/upstream/libcommon-sense-perl/current/LICENSE
Removed:
    branches/upstream/libcommon-sense-perl/current/COPYING
Modified:
    branches/upstream/libcommon-sense-perl/current/Changes
    branches/upstream/libcommon-sense-perl/current/MANIFEST
    branches/upstream/libcommon-sense-perl/current/META.yml
    branches/upstream/libcommon-sense-perl/current/README
    branches/upstream/libcommon-sense-perl/current/sense.pm

Modified: branches/upstream/libcommon-sense-perl/current/Changes
URL: http://svn.debian.org/wsvn/pkg-perl/branches/upstream/libcommon-sense-perl/current/Changes?rev=42585&op=diff
==============================================================================
--- branches/upstream/libcommon-sense-perl/current/Changes (original)
+++ branches/upstream/libcommon-sense-perl/current/Changes Sun Aug 23 20:59:46 2009
@@ -1,4 +1,10 @@
 Revision history for perl pragma common::sense.
+
+1.0   Sat Aug 22 22:08:50 CEST 2009
+	- no functional changes.
+	- really, the first version of common sense!
+        - slightly improved documentation.
+	- forgot to include license.
 
 0.04  Sun Aug  2 10:29:23 CEST 2009
 	- added "what others..." section.

Added: branches/upstream/libcommon-sense-perl/current/LICENSE
URL: http://svn.debian.org/wsvn/pkg-perl/branches/upstream/libcommon-sense-perl/current/LICENSE?rev=42585&op=file
==============================================================================
--- branches/upstream/libcommon-sense-perl/current/LICENSE (added)
+++ branches/upstream/libcommon-sense-perl/current/LICENSE Sun Aug 23 20:59:46 2009
@@ -1,0 +1,2 @@
+This module is licensed under the same terms as perl itself.
+

Modified: branches/upstream/libcommon-sense-perl/current/MANIFEST
URL: http://svn.debian.org/wsvn/pkg-perl/branches/upstream/libcommon-sense-perl/current/MANIFEST?rev=42585&op=diff
==============================================================================
--- branches/upstream/libcommon-sense-perl/current/MANIFEST (original)
+++ branches/upstream/libcommon-sense-perl/current/MANIFEST Sun Aug 23 20:59:46 2009
@@ -1,7 +1,7 @@
 README
+LICENSE
 Changes
 MANIFEST
-COPYING
 Makefile.PL
 sense.pm
 t/00_load.t

Modified: branches/upstream/libcommon-sense-perl/current/META.yml
URL: http://svn.debian.org/wsvn/pkg-perl/branches/upstream/libcommon-sense-perl/current/META.yml?rev=42585&op=diff
==============================================================================
--- branches/upstream/libcommon-sense-perl/current/META.yml (original)
+++ branches/upstream/libcommon-sense-perl/current/META.yml Sun Aug 23 20:59:46 2009
@@ -11,7 +11,7 @@
    },
    "generated_by" : "ExtUtils::MakeMaker version 6.50",
    "distribution_type" : "module",
-   "version" : "0.04",
+   "version" : "1.0",
    "name" : "common-sense",
    "author" : [],
    "license" : "unknown",

Modified: branches/upstream/libcommon-sense-perl/current/README
URL: http://svn.debian.org/wsvn/pkg-perl/branches/upstream/libcommon-sense-perl/current/README?rev=42585&op=diff
==============================================================================
--- branches/upstream/libcommon-sense-perl/current/README (original)
+++ branches/upstream/libcommon-sense-perl/current/README Sun Aug 23 20:59:46 2009
@@ -16,16 +16,19 @@
     Perl coders.
 
     no warnings
-        The dreaded warnings. Even worse, the horribly dreaded "-w" switch.
-        Even though we don't care if other people use warnings (and
+        Ah, the dreaded warnings. Even worse, the horribly dreaded "-w"
+        switch: Even though we don't care if other people use warnings (and
         certainly there are useful ones), a lot of warnings simply go
-        against the spirit of Perl, most prominently, the warnings related
-        to "undef". There is nothing wrong with "undef": it has well-defined
-        semantics, it is useful, and spitting out warnings you never asked
-        for is just evil.
+        against the spirit of Perl.
+
+        Most prominently, the warnings related to "undef". There is nothing
+        wrong with "undef": it has well-defined semantics, it is useful, and
+        spitting out warnings you never asked for is just evil.
 
         So every module needs "no warnings" to avoid somebody accidentally
         using "-w" and forcing his bad standards on our code. No will do.
+        Really, the "-w" switch should only enable wanrings for the main
+        program.
 
         Funnily enough, perllexwarn explicitly mentions "-w" (and not in a
         favourable way), but standard utilities, such as prove, or MakeMaker
@@ -33,7 +36,7 @@
 
     use strict qw(subs vars)
         Using "use strict" is definitely common sense, but "use strict
-        'refs'" definitely overshoots it's usefulness. After almost two
+        'refs'" definitely overshoots its usefulness. After almost two
         decades of Perl hacking, we decided that it does more harm than
         being useful. Specifically, constructs like these:
 
@@ -45,37 +48,49 @@
            @{ $var->[0] || [] }
 
         This is annoying, and doesn't shield against obvious mistakes such
-        as using "", so one would even have to write:
+        as using "", so one would even have to write (at least for the time
+        being):
 
            @{ defined $var->[0] ? $var->[0] :  [] }
 
         ... which nobody with a bit of common sense would consider writing.
-        Curiously enough, sometimes, perl is not so strict, as this works
+
+        Curiously enough, sometimes perl is not so strict, as this works
         even with "use strict" in scope:
 
            for (@{ $var->[0] }) { ...
 
-        If that isnt hipocrasy! And all that from a mere program!
+        If that isn't hipocrasy! And all that from a mere program!
 
     use feature qw(say state given)
         We found it annoying that we always have to enable extra features.
         If something breaks because it didn't anticipate future changes, so
         be it. 5.10 broke almost all our XS modules and nobody cared either
-        - and few modules that are no longer maintained work with newer
-        versions of Perl, regardless of use feature.
+        (or at leats I know of nobody who really complained about gratitious
+        changes - as opposed to bugs).
 
-        If your code isn't alive, it's dead, jim.
+        Few modules that are not actively maintained work with newer
+        versions of Perl, regardless of use feature or not, so a new major
+        perl release means changes to many modules - new keywords are just
+        the tip of the iceberg.
 
-    much less memory
-        Just using all those pragmas together waste <blink>*776
-        kilobytes*</blink> of precious memory in my perl, for *every single
-        perl process using our code*, which on our machines, is a lot. In
-        comparison, this module only uses *four* kilobytes (I even had to
-        write it out so it looks like more) of memory on the same platform.
+        If your code isn't alive, it's dead, jim - be an active maintainer.
+
+    mucho reduced memory usage
+        Just using all those pragmas mentioned in the SYNOPSIS together
+        wastes <blink>*776 kilobytes*</blink> of precious memory in my perl,
+        for *every single perl process using our code*, which on our
+        machines, is a lot. In comparison, this module only uses *four*
+        kilobytes (I even had to write it out so it looks like more) of
+        memory on the same platform.
 
         The money/time/effort/electricity invested in these gigabytes
         (probably petabytes globally!) of wasted memory could easily save 42
         trees, and a kitten!
+
+        Unfortunately, until everybods applies more common sense, there will
+        still often be modules that pull in the monster pragmas. But one can
+        hope...
 
 THERE IS NO 'no common::sense'!!!! !!!! !!
     This module doesn't offer an unimport. First of all, it wastes even more
@@ -93,9 +108,23 @@
     try to emulate "say" or so with perls older than 5.10 (this module, of
     course, should work with older perl versions - supporting 5.8 for
     example is just common sense at this time. Maybe not in the future, but
-    of course you can trust our common sense).
+    of course you can trust our common sense to be consistent with, uhm, our
+    opinion).
 
-WHAT OTHER PEOPLE HAVE TO SAY ABOUT THIS MODULE
+WHAT OTHER PEOPLE HAD TO SAY ABOUT THIS MODULE
+    apeiron
+
+       "... wow"
+       "I hope common::sense is a joke."
+
+    crab
+
+       "i wonder how it would be if joerg schilling wrote perl modules."
+
+    H.Merijn Brand
+
+       "Just one more reason to drop JSON::XS from my distribution list"
+
     Pista Palo
 
        "Something in short supply these days..."
@@ -133,10 +162,6 @@
 
        "THERE IS NO 'no common::sense'!!!! !!!! !!"
 
-    crab
-
-       "i wonder how it would be if joerg schilling wrote perl modules."
-
 AUTHOR
      Marc Lehmann <schmorp at schmorp.de>
      http://home.schmorp.de/

Modified: branches/upstream/libcommon-sense-perl/current/sense.pm
URL: http://svn.debian.org/wsvn/pkg-perl/branches/upstream/libcommon-sense-perl/current/sense.pm?rev=42585&op=diff
==============================================================================
--- branches/upstream/libcommon-sense-perl/current/sense.pm (original)
+++ branches/upstream/libcommon-sense-perl/current/sense.pm Sun Aug 23 20:59:46 2009
@@ -22,15 +22,18 @@
 
 =item no warnings
 
-The dreaded warnings. Even worse, the horribly dreaded C<-w> switch. Even
-though we don't care if other people use warnings (and certainly there are
-useful ones), a lot of warnings simply go against the spirit of Perl, most
-prominently, the warnings related to C<undef>. There is nothing wrong with
-C<undef>: it has well-defined semantics, it is useful, and spitting out
-warnings you never asked for is just evil.
+Ah, the dreaded warnings. Even worse, the horribly dreaded C<-w>
+switch: Even though we don't care if other people use warnings (and
+certainly there are useful ones), a lot of warnings simply go against the
+spirit of Perl.
+
+Most prominently, the warnings related to C<undef>. There is nothing wrong
+with C<undef>: it has well-defined semantics, it is useful, and spitting
+out warnings you never asked for is just evil.
 
 So every module needs C<no warnings> to avoid somebody accidentally using
-C<-w> and forcing his bad standards on our code. No will do.
+C<-w> and forcing his bad standards on our code. No will do. Really, the
+C<-w> switch should only enable wanrings for the main program.
 
 Funnily enough, L<perllexwarn> explicitly mentions C<-w> (and not in a
 favourable way), but standard utilities, such as L<prove>, or MakeMaker
@@ -39,7 +42,7 @@
 =item use strict qw(subs vars)
 
 Using C<use strict> is definitely common sense, but C<use strict
-'refs'> definitely overshoots it's usefulness. After almost two
+'refs'> definitely overshoots its usefulness. After almost two
 decades of Perl hacking, we decided that it does more harm than being
 useful. Specifically, constructs like these:
 
@@ -51,45 +54,55 @@
    @{ $var->[0] || [] }
 
 This is annoying, and doesn't shield against obvious mistakes such as
-using C<"">, so one would even have to write:
+using C<"">, so one would even have to write (at least for the time
+being):
 
    @{ defined $var->[0] ? $var->[0] :  [] }
 
 ... which nobody with a bit of common sense would consider
-writing. Curiously enough, sometimes, perl is not so strict, as this works
-even with C<use strict> in scope:
+writing.
+
+Curiously enough, sometimes perl is not so strict, as this works even with
+C<use strict> in scope:
 
    for (@{ $var->[0] }) { ...
 
-If that isnt hipocrasy! And all that from a mere program!
+If that isn't hipocrasy! And all that from a mere program!
 
 =item use feature qw(say state given)
 
 We found it annoying that we always have to enable extra features. If
 something breaks because it didn't anticipate future changes, so be
-it. 5.10 broke almost all our XS modules and nobody cared either - and few
-modules that are no longer maintained work with newer versions of Perl,
-regardless of use feature.
-
-If your code isn't alive, it's dead, jim.
-
-=item much less memory
-
-Just using all those pragmas together waste <blink>I<< B<776> kilobytes
->></blink> of precious memory in my perl, for I<every single perl process
-using our code>, which on our machines, is a lot. In comparison, this
-module only uses I<< B<four> >> kilobytes (I even had to write it out so
-it looks like more) of memory on the same platform.
+it. 5.10 broke almost all our XS modules and nobody cared either (or at
+leats I know of nobody who really complained about gratitious changes - as
+opposed to bugs).
+
+Few modules that are not actively maintained work with newer versions of
+Perl, regardless of use feature or not, so a new major perl release means
+changes to many modules - new keywords are just the tip of the iceberg.
+
+If your code isn't alive, it's dead, jim - be an active maintainer.
+
+=item mucho reduced memory usage
+
+Just using all those pragmas mentioned in the SYNOPSIS together wastes
+<blink>I<< B<776> kilobytes >></blink> of precious memory in my perl, for
+I<every single perl process using our code>, which on our machines, is a
+lot. In comparison, this module only uses I<< B<four> >> kilobytes (I even
+had to write it out so it looks like more) of memory on the same platform.
 
 The money/time/effort/electricity invested in these gigabytes (probably
 petabytes globally!) of wasted memory could easily save 42 trees, and a
 kitten!
 
+Unfortunately, until everybods applies more common sense, there will still
+often be modules that pull in the monster pragmas. But one can hope...
+
 =cut
 
 package common::sense;
 
-our $VERSION = '0.04';
+our $VERSION = '1.0';
 
 sub import {
    # no warnings
@@ -126,10 +139,22 @@
 C<say> or so with perls older than 5.10 (this module, of course, should
 work with older perl versions - supporting 5.8 for example is just common
 sense at this time. Maybe not in the future, but of course you can trust
-our common sense).
-
-
-=head1 WHAT OTHER PEOPLE HAVE TO SAY ABOUT THIS MODULE
+our common sense to be consistent with, uhm, our opinion).
+
+=head1 WHAT OTHER PEOPLE HAD TO SAY ABOUT THIS MODULE
+
+apeiron
+
+   "... wow"
+   "I hope common::sense is a joke."
+
+crab
+
+   "i wonder how it would be if joerg schilling wrote perl modules."
+
+H.Merijn Brand
+
+   "Just one more reason to drop JSON::XS from my distribution list"
 
 Pista Palo
 
@@ -168,10 +193,6 @@
 
    "THERE IS NO 'no common::sense'!!!! !!!! !!"
 
-crab
-
-   "i wonder how it would be if joerg schilling wrote perl modules."
-
 =head1 AUTHOR
 
  Marc Lehmann <schmorp at schmorp.de>
@@ -179,6 +200,5 @@
 
  Robin Redeker, "<elmex at ta-sa.org>".
 
-
 =cut
 




More information about the Pkg-perl-cvs-commits mailing list