| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Many of the files in perl are for one thing only, and hence their
embedded documentation will be for that one thing. By creating a hash
here of them, those files don't have to worry about what section that
documentation goes under, and so it can be completely changed without
affecting them.
|
|
|
|
|
|
| |
Now that we can get automatic links in perlapi, remove the redundant
stripped-down documentation that goes there in favor of the better
documentation in perlcall.
|
| |
|
| |
|
|
|
|
|
| |
This uses a new organization of sections that I came up with. I asked
for comments on p5p, but there were none.
|
| |
|
|
|
|
|
|
| |
call_argv does not use a stack pointer. This example has had the
redundant dSP since perl 5.000, presumably due to copying and
pasting from another example.
|
|
|
|
| |
Mostly these are too long verbatim lines.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The value of gimme stored in the context stack is U8.
Make all other uses in the main core consistent with this.
My primary motivation on this was that the new function cx_pushblock(),
which I gave a 'U8 gimme' parameter, was generating warnings where callers
were passing I32 gimme vars to it. Rather than play whack-a-mole, it
seemed simpler to just uniformly use U8 everywhere.
Porting/bench.pl shows a consistent reduction of about 2 instructions on
the loop and sub benchmarks, so this change isn't harming performance.
|
|
|
|
| |
This fixes a bunch of them, but there are many more
|
|
|
|
| |
or should that be "fix an typo"
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- linkify references to sections
- use EXTEND(SP, n) and PUSHs() instead of XPUSHs() where applicable
and update prose to match
- add POPu, POPul and POPpbytex to the "complete list of POP macros"
and clarify the documentation for some of the existing entries, and
a note about side-effects
- add API documentation for POPu and POPul
- use ERRSV more efficiently
- approaches to thread-safety storage of SVs.
- minor updates
|
|
|
|
|
|
|
| |
This finishes the removal of register declarations started by
eb578fdb5569b91c28466a4d1939e381ff6ceaf4. It neglected the ones in
function parameter declarations, and didn't include things in dist, ext,
and lib, which this does include
|
| |
|
| |
|
|
|
|
|
|
| |
This makes many documents more consistent in their pod formatting. Don't trim
blank lines between verbatim blocks and =item, as removing them makes the (raw)
pod harder to read.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Whilst ‘whilst’ is nice, the sentence as it was before this change
indicated that the stack was in the call_pv call (whatever
that means).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It is not good style to join two independent clauses with a comma, it
just does not read well.
Hyphenate ‘multi word’ adjective
Inconsistent use of - vs. -- for a dash.
Missing commas
Other punctuation errors
Terribly Inconsistent capitalisation in =head2’s
Other grammatical errors or unclear phrases
|
|
|
|
|
|
| |
Multi word adjectives should be hyphenated.
A preposition should not be used like it’s a conjunction.
|
|
|
|
|
|
|
|
| |
Commit 2f8edad0d37e91319b6ba10b3745327ea49c179 made G_ARRAY
equal to G_SCALAR | G_VOID, contrary to perlcall.pod.
Bring the documentation up to date and add a test to prevent a similar
(although unlikely) accident in the future.
|
| |
|
|
|
|
|
|
|
|
|
| |
Makes the G_KEEPERR logic more consistent, and in particular make it
sensibly handle non-string exceptions. An exception in a destructor
is now always emitted as a warning, and never copied or merged into
$@ of the surrounding context. No more clobbering exceptions being
handled elsewhere, and no more double reporting. This fixes the rest of
[perl #74538].
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I looked at all the instances of spaces around -- and in most cases
converted the sentences to use more appropriate punctuation. In
general, the -- in the perl docs seem to be there only to make
really complicated and really long sentences.
I didn't look at the closed em-dashes. They probably have the same
sentence-complexity problem.
I left some open em-dashes in place. Those are the ones used in
lists.
|
| |
|
|
|
| |
p4raw-id: //depot/perl@34197
|
|
|
|
|
| |
Message-ID: <20051031214827.GH24416@accognoscere.homeunix.org>
p4raw-id: //depot/perl@26073
|
|
|
|
|
| |
Message-ID: <20051108190234.GA25953@rpc142.cs.man.ac.uk>
p4raw-id: //depot/perl@26054
|
|
|
|
|
| |
(noticed by Robin Houston)
p4raw-id: //depot/perl@26012
|
|
|
|
|
| |
Message-ID: <20051029203307.GA8869@rpc142.cs.man.ac.uk>
p4raw-id: //depot/perl@25953
|
|
|
| |
p4raw-id: //depot/perl@23203
|
|
|
| |
p4raw-id: //depot/perl@12338
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Subject: [PATCH] Code clean up for perlboot.pod
Date: Tue, 2 Oct 2001 19:24:43 -0400
Message-ID: <20011002192443.B2163@stupid.geeknest.com>
Subject: [PATCH] Code clean up for perlbot.diff
From: Casey West <casey@geeknest.com>
Date: Tue, 2 Oct 2001 19:25:22 -0400
Message-ID: <20011002192522.C2163@stupid.geeknest.com>
Subject: [PATCH] Code clean up for perlcall.pod
From: Casey West <casey@geeknest.com>
Date: Tue, 2 Oct 2001 19:25:57 -0400
Message-ID: <20011002192557.D2163@stupid.geeknest.com>
Subject: [PATCH] Code clean up for perldata.pod
From: Casey West <casey@geeknest.com>
Date: Tue, 2 Oct 2001 19:26:29 -0400
Message-ID: <20011002192629.E2163@stupid.geeknest.com>
Subject: [PATCH] Code clean up for perldbmfilter.pod
From: Casey West <casey@geeknest.com>
Date: Tue, 2 Oct 2001 19:26:59 -0400
Message-ID: <20011002192659.F2163@stupid.geeknest.com>
Subject: [PATCH] Code clean up for perlebcdic.pod
From: Casey West <casey@geeknest.com>
Date: Tue, 2 Oct 2001 19:27:37 -0400
Message-ID: <20011002192737.G2163@stupid.geeknest.com>
p4raw-id: //depot/perl@12313
|
|
|
|
|
| |
Message-Id: <20010208151146.0937BC97E@little-roots.geneanet.org>
p4raw-id: //depot/perl@8745
|
|
|
|
|
| |
Message-ID: <20000804002244.A5924@ilmd.chetlin.org>
p4raw-id: //depot/perl@6522
|
|
|
|
|
| |
<wolfgang.laun@alcatel.at>)
p4raw-id: //depot/perl@5715
|
|
|
| |
p4raw-id: //depot/perl@5371
|
|
|
| |
p4raw-id: //depot/perl@4711
|
|
|
| |
p4raw-id: //depot/perl@3460
|
|
|
|
|
|
|
|
|
|
|
| |
Date: Wed, 3 Feb 1999 05:24:55 -0500 (EST)
Message-ID: <Pine.SOL.3.91.990203051924.302A-100000@soc11.acpub.duke.edu>
Subject: [PATCH]5.005_54 (DOC) fix many typos
--
Date: Wed, 3 Feb 1999 08:53:53 -0500 (EST)
Message-ID: <Pine.SOL.3.91.990203085157.895A-100000@soc11.acpub.duke.edu>
Subject: [PATCH]5.005_54 (DOC) typos
p4raw-id: //depot/perl@2929
|
|
|
|
|
|
|
|
|
|
|
| |
Subject: bad L<> links
Reply-to: tchrist@perl.com
To: perlbug@jhereg.perl.com
Message-Id: <199808111658.KAA00484@jhereg.perl.com>
The ones not fixed may require darker Pod::HTML magic,
for example the perlguts.html#tags should work fine, IMHO.
p4raw-id: //depot/cfgperl@2437
|
|
|
|
|
|
|
|
| |
avoid most uses of PL_na (which is much more inefficient than a
simple local); update docs to suit; PL_na now being thr->Tna may
be a minor compatibility issue for extensions--will require dTHR
outside of XSUBs (those get automatic dTHR)
p4raw-id: //depot/perl@2387
|
|
|
|
|
| |
Message-Id: <199807271134.NAA24475@dorlas.elsevier.nl>
p4raw-id: //depot/maint-5.005/perl@1680
|
|
|
|
|
|
| |
from Jon Orwant <orwant@media.mit.edu>; update guts documentation
to reflect PL_* changes; is this *it* for 5.005?
p4raw-id: //depot/perl@1646
|
|
|
|
|
| |
Message-Id: <199807170949.LAA18099@lion.plab.ku.dk>
p4raw-id: //depot/perl@1558
|
|
|
|
|
| |
p4raw-link: @897 on //depot/maint-5.004/perl: f06f9b6fc5a686f0169ee2a91b32d5e7125a44ae
p4raw-id: //depot/win32/perl@974
|
|
|
| |
p4raw-id: //depot/win32/perl@796
|