r70552 - in /trunk/libclass-prototyped-perl/debian: changelog control

[rra at users.alioth.debian.org]

Author: rra
Date: Sat Mar  5 23:22:49 2011
New Revision: 70552

URL: http://svn.debian.org/wsvn/pkg-perl/?sc=1&rev=70552
Log:
* Rewrite the package long description to digest and summarize the
  information and avoid long quotes from the module documentation.

Modified:
    trunk/libclass-prototyped-perl/debian/changelog
    trunk/libclass-prototyped-perl/debian/control

Modified: trunk/libclass-prototyped-perl/debian/changelog
URL: http://svn.debian.org/wsvn/pkg-perl/trunk/libclass-prototyped-perl/debian/changelog?rev=70552&op=diff
==============================================================================
--- trunk/libclass-prototyped-perl/debian/changelog (original)
+++ trunk/libclass-prototyped-perl/debian/changelog Sat Mar  5 23:22:49 2011
@@ -23,6 +23,8 @@
     pointless for a source package that only builds arch-independent
     binary packages.
   * Fix a spelling error in the POD documentation reported by Lintian.
+  * Rewrite the package long description to digest and summarize the
+    information and avoid long quotes from the module documentation.
 
  -- gregor herrmann <gregoa at debian.org>  Sun, 16 Nov 2008 20:40:41 +0100
 

Modified: trunk/libclass-prototyped-perl/debian/control
URL: http://svn.debian.org/wsvn/pkg-perl/trunk/libclass-prototyped-perl/debian/control?rev=70552&op=diff
==============================================================================
--- trunk/libclass-prototyped-perl/debian/control (original)
+++ trunk/libclass-prototyped-perl/debian/control Sat Mar  5 23:22:49 2011
@@ -18,19 +18,15 @@
  object, and also have objects inherit their behavior and state from
  another object.
  .
- The structure of an object is inspected and modified through *mirrors*,
+ Class::Prototyped borrows heavily from the programming language Self.
+ The structure of an object is inspected and modified through mirrors,
  which are created by calling "reflect" on an object or class that
- inherits from "Class::Prototyped".
+ inherits from Class::Prototyped.
  .
- The author says: 'When I reach for "Class::Prototyped", it's generally 
- because I really need it. When the cleanest way of solving a problem is
- for the code that uses a module to subclass from it, that is generally
- a sign that "Class::Prototyped" would be of use. If you find yourself 
- avoiding the problem by passing anonymous subroutines as parameters
- to the "new" method, that's another good sign that you should be using 
- prototype based programming. If you find yourself storing anonymous 
- subroutines in databases, configuration files, or text files, and then 
- writing infrastructure to handle calling those anonymous subroutines,
- that's yet another sign. When you expect the people using your module
- to want to change the behavior, override subroutines, and so forth,
- that's a sign'.
+ Prototype-based programming is most useful when the cleanest way for code
+ to use a module is to subclass it, or when one finds oneself avoiding
+ this by passing anonymous subroutines as parameters to "new".
+ Prototype-based programming is also useful in situations that otherwise
+ require storing anonymous subroutines in databases, configuration files,
+ or text files, or when users of a module are expected to override
+ subroutines to change its behabior.