From: "John P. Linderman" <jpl@research.att.com>
Date: Wed, 27 Aug 2003 08:10:12 -0400 (EDT)
Message-Id: <
200308271210.IAA23907@raptor.research.att.com>
Subject: typo in pod/perlnewmod.pod [PATCH]
From: "John P. Linderman" <jpl@research.att.com>
Date: Wed, 27 Aug 2003 09:07:12 -0400 (EDT)
Message-Id: <
200308271307.JAA46955@raptor.research.att.com>
Subject: [PATCH] document the location of byacc
From: Dave Mitchell <davem@fdgroup.com>
Date: Wed, 27 Aug 2003 14:26:50 +0100
Message-ID: <
20030827132650.GA23144@fdgroup.com>
p4raw-id: //depot/perl@20917
=head2 make run_byacc
-If you have byacc-1.8.2 (available from CPAN), and if there have been
-changes to F<perly.y>, you can regenerate the F<perly.c> file. The
+If you have byacc-1.8.2 (available from CPAN as
+http://www.cpan.org/src/misc/perl-byacc1.8.2.tar.gz), and if there have
+been changes to F<perly.y>, you can regenerate the F<perly.c> file. The
run_byacc makefile target does this by running byacc and then applying
some patches so that byacc dynamically allocates space, rather than
having fixed limits. This patch is handled by the F<perly.fixer>
A file full of regular expressions to exclude when using 'make
manifest' to generate the MANIFEST. These regular expressions
-are checked against each filepath found in the distrubtion (so
+are checked against each filepath found in the distribution (so
you're matching against "t/foo.t" not "foo.t").
Here's a sample:
You might love it. You might feel that everyone else needs it. But there
might not actually be any real demand for it out there. If you're unsure
-about the demand you're module will have, consider sending out feelers
+about the demand your module will have, consider sending out feelers
on the C<comp.lang.perl.modules> newsgroup, or as a last resort, ask the
modules list at C<modules@perl.org>. Remember that this is a closed list
with a very long turn-around time - be prepared to wait a good while for