I'm cc-ing this to p6 because there doesn't seem to be anyone left on p5p.
Let me deal with the easy bit first. I've added a convenience function
called "warnings::warnif" that allows you to write this:
warnings::warnif($category, "message") ;
instead of this:
if (warnings::enabled($ca
From: Simon Cozens [mailto:[EMAIL PROTECTED]]
> On Sun, Aug 13, 2000 at 09:36:48PM -0400, Ronald J Kimball wrote:
> > On Sun, Aug 13, 2000 at 09:04:41PM +0100, Paul Marquess wrote:
> > > I'm cc-ing this to p6 because there doesn't seem to be anyone left on
p5p.
&g
ffectively, it allows
> one to use
> the full power of Perl as its own, recursively applied, macro language.
>
> The Filter::Util::Call module (by Paul Marquess) provides a usable Perl
> interface to source filtering, but it is not nearly as simple as
> it could be.
>
> T
From: Damian Conway [mailto:[EMAIL PROTECTED]]
...
>
> No. That's my point. I want to match BANG followed by maximal whitespace
> followed by another BANG. But a line-by-line filter fails dismally if that
> maximal whitespace contains a newline.
>
> Admittedly this particular example is contrived
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
...
>
> The basic usefulness of warnings is not in question. This is about
> the *perception* of their utility. Warnings are only useful if the
> user heeds them. The question is, will having them on by default make
> the user more or less l
> The behaviour is explained quite well in E5 I think.
Is that the "soon to be released" E5?
Paul
> > Is that the "soon to be released" E5?
>
> No, that's the "to be released today" E5.
>
> ;-)
Yy!!
