[ANNOUNCE] Pod::StdParser, Pod::Tests proof of concept

2000-09-04 Thread Barrie Slaymaker
In http://slaysys.com/src/Pod-StdParser-0.001.tar.gz you should find an experimental Pod::StdParser, with a Pod::Tests and a tweaked Pod::Parser and a Pod::Text that's undergoing a transplant from Pod::Select to Pod::StdParser (yes, I know, that'd break Pod::Usage). I've disabled the Makefile ins

Re: RFC 183 (v1) "=for testing" - Embedded tests

2000-09-04 Thread Barrie Slaymaker
Michael G Schwern wrote: > > On Fri, Sep 01, 2000 at 12:18:32AM -0400, Barrie Slaymaker wrote: > > Here's a quick take on a Pod::Tests, I threw it together as part of my =also > > prototype code. > > Looking at the docs... umm, how do you use it? Let's assume I don't > know how to use Pod::Sele

Re: Pre-RFC - "use warnings" by default for all non-one-liners

2000-09-04 Thread Michael G Schwern
On Mon, Sep 04, 2000 at 10:40:31PM -0400, Chaim Frenkel wrote: > This has been shot down repeatedly, why should things change? Why should we write Perl 6? I propose warnings on largely because my first answer to most questions about why a program won't work is "Did you turn warnings on?" and the

Re: Pre-RFC - "use warnings" by default for all non-one-liners

2000-09-04 Thread Chaim Frenkel
> "MGS" == Michael G Schwern <[EMAIL PROTECTED]> writes: MGS> I wanted to run this by the QA group before letting it loose on the MGS> language folks. MGS> "use warnings" by default for all non-one-liners. This has been shot down repeatedly, why should things change? There is a related dis

Pre-RFC - "use warnings" by default for all non-one-liners

2000-09-04 Thread Michael G Schwern
I wanted to run this by the QA group before letting it loose on the language folks. =pod =head1 TITLE "use warnings" by default for all non-one-liners. =head1 VERSION Maintainer: Michael G Schwern <[EMAIL PROTECTED]> Date: Mon Sep 4 00:02:12 EDT 2000 Version:1.0 Maili