This is a live mirror of the Perl 5 development currently hosted at
https://github.com/perl/perl5
https://perl5.git.perl.org
/
perl5.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
Update IO-Compress to CPAN version 2.040
[perl5.git]
/
pod
/
perlclib.pod
diff --git
a/pod/perlclib.pod
b/pod/perlclib.pod
index
e89a67a
..
0785577
100644
(file)
--- a/
pod/perlclib.pod
+++ b/
pod/perlclib.pod
@@
-99,12
+99,12
@@
There is no equivalent to C<fgets>; one should use C<sv_gets> instead:
Instead Of: Use:
Instead Of: Use:
- t* p = malloc(n) New(id, p, n, t)
- t* p = calloc(n, s) Newz(id, p, n, t)
+ t* p = malloc(n) New
x
(id, p, n, t)
+ t* p = calloc(n, s) New
x
z(id, p, n, t)
p = realloc(p, n) Renew(p, n, t)
memcpy(dst, src, n) Copy(src, dst, n, t)
memmove(dst, src, n) Move(src, dst, n, t)
p = realloc(p, n) Renew(p, n, t)
memcpy(dst, src, n) Copy(src, dst, n, t)
memmove(dst, src, n) Move(src, dst, n, t)
- memcpy
/*(struct foo *)
StructCopy(src, dst, t)
+ memcpy
(dst, src, sizeof(t))
StructCopy(src, dst, t)
memset(dst, 0, n * sizeof(t)) Zero(dst, n, t)
memzero(dst, 0) Zero(dst, n, char)
free(p) Safefree(p)
memset(dst, 0, n * sizeof(t)) Zero(dst, n, t)
memzero(dst, 0) Zero(dst, n, char)
free(p) Safefree(p)
@@
-132,15
+132,18
@@
instead of raw C<char *> strings:
Note also the existence of C<sv_catpvf> and C<sv_vcatpvfn>, combining
concatenation with formatting.
Note also the existence of C<sv_catpvf> and C<sv_vcatpvfn>, combining
concatenation with formatting.
-Sometimes instead of zeroing the allocated heap by using Newz() you
+Sometimes instead of zeroing the allocated heap by using New
x
z() you
should consider "poisoning" the data. This means writing a bit
pattern into it that should be illegal as pointers (and floating point
numbers), and also hopefully surprising enough as integers, so that
any code attempting to use the data without forethought will break
sooner rather than later. Poisoning can be done using the Poison()
should consider "poisoning" the data. This means writing a bit
pattern into it that should be illegal as pointers (and floating point
numbers), and also hopefully surprising enough as integers, so that
any code attempting to use the data without forethought will break
sooner rather than later. Poisoning can be done using the Poison()
-macro
, which has similar arguments as
Zero():
+macro
s, which have similar arguments to
Zero():
- Poison(dst, n, t)
+ PoisonWith(dst, n, t, b) scribble memory with byte b
+ PoisonNew(dst, n, t) equal to PoisonWith(dst, n, t, 0xAB)
+ PoisonFree(dst, n, t) equal to PoisonWith(dst, n, t, 0xEF)
+ Poison(dst, n, t) equal to PoisonFree(dst, n, t)
=head2 Character Class Tests
=head2 Character Class Tests
@@
-173,9
+176,9
@@
table, C<c> is a C<char>, and C<u> is a Unicode codepoint.
atof(s) Atof(s)
atol(s) Atol(s)
atof(s) Atof(s)
atol(s) Atol(s)
- strtod(s,
*
p) Nothing. Just don't use it.
- strtol(s,
*p, n) Strtol(s, *
p, n)
- strtoul(s,
*p, n) Strtoul(s, *
p, n)
+ strtod(s,
&
p) Nothing. Just don't use it.
+ strtol(s,
&p, n) Strtol(s, &
p, n)
+ strtoul(s,
&p, n) Strtoul(s, &
p, n)
Notice also the C<grok_bin>, C<grok_hex>, and C<grok_oct> functions in
F<numeric.c> for converting strings representing numbers in the respective
Notice also the C<grok_bin>, C<grok_hex>, and C<grok_oct> functions in
F<numeric.c> for converting strings representing numbers in the respective
@@
-205,5
+208,5
@@
For C<signal>/C<sigaction>, use C<rsignal(signo, handler)>.
=head1 SEE ALSO
=head1 SEE ALSO
-
C<perlapi>, C<perlapio>, C
<perlguts>
+
L<perlapi>, L<perlapio>, L
<perlguts>