On Dec 24, 2004, at 5:46 AM, Ken Williams wrote:
I do think that the real root of this problem is that mod_perl 2 is
essentially a different beast from mod_perl 1, but it's being crammed
into the same namespace. That has caused many people pain for a long
time already - for Mason we always got
On Thu, Dec 23, 2004 at 07:07:29PM -0600, Craig A. Berry wrote:
Nicholas Clark wrote:
What's the best way to patch Configure.com to create the line
userelocatableinc='undef'
in config.sh?
This'll do it.
Thanks, applied (23677)
Nicholas Clark
Stas Bekman wrote:
Care to submit a patch ?
--- sv.c.orig 2004-12-23 16:24:21.255855616 -0500
+++ sv.c2004-12-23 16:27:45.305002079 -0500
@@ -5406,6 +5406,9 @@
See Csv_magicext (which Csv_magic now calls) for a description of the
handling of the Cname and Cnamlen arguments.
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #33173]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=33173
This is a bug report for perl from [EMAIL PROTECTED],
generated with the
On Fri, 24 Dec 2004 09:31:01 +0100, Jos I. Boumans [EMAIL PROTECTED]
said:
On Dec 24, 2004, at 5:46 AM, Ken Williams wrote:
I feel like any solutions we
try to hurry into CPAN to try to band-aid the problem are going to
be ad-hoc and regrettable.
Again, I concur -- as i've
Hi there,
Over a year and a half ago, I wrote POD in 5 minutes. There was no POD
tutorial, and people had said that perlpod was a bit overwhelming for a
POD-newbie. This tutorial has already helped a lot of people move from
text or HTML files to POD.
I first posted it to Perl Monks 2003-04-23,
Andreas J Koenig wrote:
On Fri, 24 Dec 2004 09:31:01 +0100, Jos I. Boumans [EMAIL
PROTECTED] said:
On Dec 24, 2004, at 5:46 AM, Ken Williams wrote:
I feel like any solutions we
try to hurry into CPAN to try to band-aid the problem are going to
be ad-hoc and regrettable.
Op een grimmige herfstdag (Thursday 23 December 2004 11:07),schreef Abe
Timmerman:
Automated smoke report for 5.9.2 patch 23670
yola: Pentium III (Coppermine) (GenuineIntel 731MHz) (i686/1 cpu)
onlinux - 2.4.21-1 [redhat]
using ccache gcc version 3.2.2 20030222 (Red Hat
On Sun, 19 Dec 2004 14:17:22 -0500, Stas Bekman [EMAIL PROTECTED] said:
Well, the suggested plan is something that we (not Stas) have come up with
here on p5p when this issue was discussed several times over the last few
years, it just fell through the cracks and now it has re-emerged
I wrote:
(/puts his hat guy responsible for the package management software at
Mandrakesoft)
Fourded (what's the verb for four anyway ?)
I realize that this may sound harsh, given that many people are aware
of this issue with mod_perl (and eventually other modules (IIRC GD has
more or less
Automated smoke report for 5.9.2 patch 23678 on bsd/os - 4.1 (i386/1 cpu)
(fixit.xs4all.nl) using version
Report by Test::Smoke v1.18.09 (perl 5.00503) [3 hours 3 minutes]
O = OK F = Failure(s), extended report at the bottom
X = test(s) failed under TEST but not under harness
? = still running
On Thu, Dec 23, 2004 at 09:12:43AM -0600, Steve Peters wrote:
On Thu, Dec 23, 2004 at 03:46:00AM -0600, [EMAIL PROTECTED] wrote:
Automated smoke report for 5.9.2 patch 23670
mccoy.peters.homeunix.org: Intel Pentium III (GenuineIntel 686-class,
512KB L2 cache) (i386/1 cpu)
on
Ton Hospel wrote:
While trying to do
...
if (condition) PUSHMARK(SP);
...
I didn't work at all until I finally realized that PUSHMARK
is not protected by STMT_START and STMT_END
Here is a patch for pp.h (5.8.5 version) that adds the missing cases:
Thanks, applied as #23680 to blead.
[EMAIL PROTECTED] (via RT) wrote:
Below is an updated version of shellwords.pl with the following
changes:
Thanks, applied as #23681 to blead.
- keep taint
- use the local *_ = ref trick to defeat tied $_
- use my variables instead of local, and drop the now unneeded internal
package
-
Ken == Ken Williams [EMAIL PROTECTED] writes:
Ken That's *not* a very good reason to introduce a new module with a new
Ken interface using an old namespace.
Hear hear. This is the source of the problem. mod_perl2 *is* a
different beasty, but Stas and the team have incorrectly reused names
On Fri, Dec 24, 2004 at 11:12:05AM +0100, Juerd wrote:
This looks like a very helpful tutorial. I just have a few nits... :)
=head1 NAME
perlpodtut - Plain Old Documentation in 5 minutes
=head1 DESCRIPTION
This short tutorial will teach you how to write documentation with POD. POD
Ronald J Kimball [EMAIL PROTECTED] writes:
On Fri, Dec 24, 2004 at 11:12:05AM +0100, Juerd wrote:
=head2 Lists
An example is much clearer than an explanation here.
=head2 Methods
=over 12
I think that should be =over 4, since the example shows an indent of 4 from
the
On Fri, Dec 24, 2004 at 11:12:05AM +0100, Juerd wrote:
=head2 Code examples
Indented paragraphs render as code, with indenting intact. It's that easy!
What does it mean for something to render as code? I think a reader will
better understand with no extra formatting or as plain text.
Michael G Schwern [EMAIL PROTECTED] writes:
On Fri, Dec 24, 2004 at 11:12:05AM +0100, Juerd wrote:
And there are F, S, X and Z, but they're rarely used so not worth
explaining in a simple tutorial.
F is, I think, what you're supposed to use for URLs and email addresses
and the like (in
On Fri, Dec 24, 2004 at 11:16:57AM -0800, Russ Allbery wrote:
=head1 LICENSE
This is released under the Artistic License. See Lperlartistic.
Since people like to cut paste, this should probably be the standard
same as Perl wording plus a copyright notice.
This should be
Ronald J Kimball skribis 2004-12-24 11:56 (-0500):
=item SYNOPSIS
means see together and shows example usage.
A synopsis is a brief summary. The derivation of the word doesn't seem
useful here.
Overview is more correct, I think. And because in typical POD documents,
the DESCRIPTION part
[EMAIL PROTECTED] (Andreas J Koenig) writes:
To map this down to perl5 is challenging (as you know) and will have
to deal with tradeoffs. The mod_perl community seems to have made the
firm decision that the namespaces of all collected modules will stay
the same. That's fine by me. But it's
Ronald J Kimball wrote:
On Fri, Dec 24, 2004 at 11:12:05AM +0100, Juerd wrote:
This looks like a very helpful tutorial. I just have a few nits... :)
yeay, with following addition(s)
=head2 Headings in POD
Logical structure is important. So we use headings. There are four levels, and
this
Michael G Schwern skribis 2004-12-24 14:11 (-0500):
Indented paragraphs render as code, with indenting intact. It's that easy!
What does it mean for something to render as code? I think a reader will
better understand with no extra formatting or as plain text.
You're right. Same is true for
This should be =head1 COPYRIGHT AND LICENSE to fit what's done
elsewhere
Google hit counts, with filetype:pod
head1 license -head1 license and copyright 183
head1 copyright -head1 copyright and license 4180
head1 copyright and license 105
head1 license and copyright
Juerd [EMAIL PROTECTED] writes:
Google hit counts, with filetype:pod
head1 license -head1 license and copyright 183
head1 copyright -head1 copyright and license 4180
head1 copyright and license 105
head1 license and copyright2
I don't
On Fri, Dec 24, 2004 at 08:57:14PM +0100, Juerd wrote:
I'm thinking of removing my email address entirely from all my modules,
because module documentation is too wide spread. Anyone with at least a
nanobrain can find out many ways to contact me.
As long as there's contact information on
We have a situation where we need to add more than one PERL_MAGIC_ext
magic to an object. sv_magicext which allows to do that is available
starting from 5.8.x+. What do I do if I need to support 5.6.x?
Thanks.
--
__
Stas Bekman
We use the C=head1 .. C=head4 commands. (They are called Icommand
paragraphs officially. They are paragraphs because they're separated from
the rest of the POD by blank lines.)
I dont see sufficient value in explaining the official name.
I do, and think it's *VERY* important to include such
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #33180]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=33180
This is a bug report for perl from [EMAIL PROTECTED],
generated with the
Currently if you do:
my $in = f\xfezz;
utf8::upgrade($in);
print Old in='$in'\n;
print unpack(H*, $in), \n;
read(STDIN, $in, 3, 2);
print Now in='$in'\n;
print unpack(H*, $in), \n;
print is utf8:, utf8::is_utf8($in) ? 1 : 0, \n;
and type abc as input, you get:
Old in='fþzz'
66c3be7a7a
abc
Now
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Ton Hospel) writes:
$buf = substr($buf, $off);
Oops, that should be $buf = substr($buf, 0, $off);
# With the current semantics for the raw/unicode-ness of the filehandle:
$rc = read($fh, my $tmp, $len);
if ($rc)
On Fri, 24 Dec 2004 22:56:09 +0100, Juerd [EMAIL PROTECTED] wrote:
* see together
And actually every single word that can be seen as Perl jargon.
synopsis is not Perl jargon, it's a simple english word, a fancy way to
say summary, and stating that it's Greek for together, with the eyes
is yes,
33 matches
Mail list logo
