Just some brief comments... $0.02 or some such. :)
-R
Quoting Dave Mitchell <[EMAIL PROTECTED]>:
> =item *
>
> "K&R" style for indenting control constructs: ie the closing C<}>
> should
> line up with the opening C etc.
You should provide a short example here - K&R has lots of nasties, you
> "DC" == Damian Conway <[EMAIL PROTECTED]> writes:
DC> One might also envisage a C pragma to require
DC> that all lexicals be typed.
do you mean lexical params in a sub signature? or all lexicals in the
current scope which contains the pragma?
required typing for all lexicals feels too
> "BD" == Brent Dax <[EMAIL PROTECTED]> writes:
BD> # From: Uri Guttman [mailto:[EMAIL PROTECTED]]
BD> # use strict 'typing' ;
BD> #
BD> # my $foo = Dog.new() ;
BD> #
BD> # that fails at compile time.
BD> #
BD> # my Dog $spot = Dog.new() ;
BD> #
BD>
> "BD" == Brent Dax <[EMAIL PROTECTED]> writes:
BD> # BD> my $rex=Dog.new;#ok at
BD> # this point...
BD> #
BD> # BD> $spot.bark(); #ok
BD> # BD> $fido.bark(); #ok
BD> # BD> $rex.bark();
I just subscribed, so forgive me if this has been covered before (I haven't
read all of the archives yet)
STYLE:
> There should be tools, guidelines and processes to assist authors in writing
> quality modules. See also [EMAIL PROTECTED]
> Specifically:
> Style guide
> Naming guidelines
I kno
On 8/24/01 11:52 PM, John Siracusa wrote:
> I mentioned this on another list, and I thought I'd bring it up here as
> well. I think NeXT-style "bundles" offer an interesting solution for
> keeping several versions of a single library installed at the same time,
> with well-defined major/minor ver
