a DBM database it always writes the key and value as strings. So when
you use this:
- $hash{12345} = "soemthing" ;
+ $hash{12345} = "something" ;
the key 12345 will get stored in the DBM database as the 5 byte string
"12345". If you actually want the key to be stored in the DBM database
8 'this'
9 'that'
-That's not much help, a couple of welcome's in there, but no indication of
+That's not much help, a couple of welcomes in there, but no indication of
which are keys, and which are values, it's just a listed array dump and, in
this case, not particularly helpful. The trick here, is to use a B<reference>
to the data structure:
Adds an action (Perl command) to happen after the prompt when you've
just given a command to return to executing the script. A multi-line
-command may be entered by slackbashing the newlines.
+command may be entered by backslashing the newlines.
=item { ?
(W internal) The internal sv_replace() function was handed a new SV with
a reference count of other than 1.
-=item Reference to nonexistant group before << HERE in regex m/%s/
+=item Reference to nonexistent group before << HERE in regex m/%s/
(F) You used something like C<\7> in your regular expression, but there are
not at least seven sets of capturing parentheses in the expression. If you
=head1 BUGS
This pod document contains literal Latin 1 characters and may encounter
-translation difficulties. In particular one populer nroff implementation
+translation difficulties. In particular one popular nroff implementation
was known to strip accented characters to their unaccented counterparts
while attempting to view this document through the B<pod2man> program
(for example, you may see a plain C<y> rather than one with a diaeresis
If BITS is 16 or more, bytes of the input string are grouped into chunks
of size BITS/8, and each group is converted to a number as with
-pack()/unpack() with big-endian formats C<n>/C<N> (and analoguously
+pack()/unpack() with big-endian formats C<n>/C<N> (and analogously
for BITS==64). See L<"pack"> for details.
If bits is 4 or less, the string is broken into bytes, then the bits
sv_utf8_upgrade(left);
If you do this in a binary operator, you will actually change one of the
-strings that came into the operator, and, while it shouldn't be noticable
+strings that came into the operator, and, while it shouldn't be noticeable
by the end user, it can cause problems.
Instead, C<bytes_to_utf8> will give you a UTF8-encoded B<copy> of its
string argument. This is useful for having the data available for
-comparisons and so on, without harming the orginal SV. There's also
+comparisons and so on, without harming the original SV. There's also
C<utf8_to_bytes> to go the other way, but naturally, this will fail if
the string contains any characters above 255 that can't be represented
in a single byte.
macro to force a PV. As a side effect, C<tlen> gets set to the current
value of the PV, and the PV itself is returned to C<junk>.
-In line 7, we make sure that the SV will have enough room to accomodate
+In line 7, we make sure that the SV will have enough room to accommodate
the old string, the new string and the null terminator. If C<LEN> isn't
big enough, C<SvGROW> will reallocate space for us.
sprintf "%vd", pack("C0U*",1,20,300,4000);
print "ok $test\n"; $test++;
-Musn't forget to change the number of tests which appears at the top, or
+Mustn't forget to change the number of tests which appears at the top, or
else the automated tester will get confused:
-print "1..156\n";
To find out I<all> modules installed on your system, including
those without documentation or outside the standard release,
-jus tdo this:
+just do this:
% find `perl -e 'print "@INC"'` -name '*.pm' -print
Once you've ensured that your module passes its own tests - always a
good thing to make sure - you can C<make dist>, and the Makefile will
-hopefully produce you a nice tarball of your module, ready for upliad.
+hopefully produce you a nice tarball of your module, ready for upload.
=item Upload the tarball
=item *
AS/400 Perl information at
-ttp://as400.rochester.ibm.com/
+http://as400.rochester.ibm.com/
as well as on CPAN in the F<ports/> directory.
=back
http firewall, ftp firewall, One way visibility, SOCKS, IP Masquerade
-=item Configuring lynx or ncftp for going throught the firewall
+=item Configuring lynx or ncftp for going through the firewall
=back
=item Warnings
-multiple occurence of link target I<name>, line containing nothing but
+multiple occurrence of link target I<name>, line containing nothing but
whitespace in paragraph, file does not start with =head, No numeric
argument for =over, previous =item has no contents, preceding non-item
paragraph(s), =item type mismatch (I<one> vs. I<two>), I<N> unescaped
projects / p5sagit/p5-mst-13.2.git / commitdiff