summaryrefslogtreecommitdiff
path: root/Master/tlpkg/tlperl/lib/pods/perlxstut.pod
diff options
context:
space:
mode:
Diffstat (limited to 'Master/tlpkg/tlperl/lib/pods/perlxstut.pod')
-rw-r--r--Master/tlpkg/tlperl/lib/pods/perlxstut.pod20
1 files changed, 6 insertions, 14 deletions
diff --git a/Master/tlpkg/tlperl/lib/pods/perlxstut.pod b/Master/tlpkg/tlperl/lib/pods/perlxstut.pod
index 62bef3b0c5f..91c13ed358f 100644
--- a/Master/tlpkg/tlperl/lib/pods/perlxstut.pod
+++ b/Master/tlpkg/tlperl/lib/pods/perlxstut.pod
@@ -198,14 +198,6 @@ been deleted):
You can safely ignore the line about "prototyping behavior" - it is
explained in L<perlxs/"The PROTOTYPES: Keyword">.
-If you are on a Win32 system, and the build process fails with linker
-errors for functions in the C library, check if your Perl is configured
-to use PerlCRT (running B<perl -V:libc> should show you if this is the
-case). If Perl is configured to use PerlCRT, you have to make sure
-PerlCRT.lib is copied to the same location that msvcrt.lib lives in,
-so that the compiler can find it on its own. msvcrt.lib is usually
-found in the Visual C compiler's lib directory (e.g. C:/DevStudio/VC/lib).
-
Perl has its own special way of easily writing test scripts, but for this
example only, we'll create our own test script. Create a file called hello
that looks like this:
@@ -228,7 +220,7 @@ and we should see the following output:
=head2 EXAMPLE 2
Now let's add to our extension a subroutine that will take a single numeric
-argument as input and return 0 if the number is even or 1 if the number
+argument as input and return 1 if the number is even or 0 if the number
is odd.
Add the following to the end of Mytest.xs:
@@ -732,7 +724,7 @@ description of an XSUB:
Note that in contrast with L<"EXAMPLE 1">, L<"EXAMPLE 2"> and L<"EXAMPLE 3">,
this description does not contain the actual I<code> for what is done
-is done during a call to Perl function foo(). To understand what is going
+during a call to Perl function foo(). To understand what is going
on here, one can add a CODE section to this XSUB:
double
@@ -1023,8 +1015,8 @@ put these declarations on top.)
This routine also returns a different number of arguments depending on the
success or failure of the call to statfs. If there is an error, the error
number is returned as a single-element array. If the call is successful,
-then a 9-element array is returned. Since only one argument is passed into
-this function, we need room on the stack to hold the 9 values which may be
+then a 7-element array is returned. Since only one argument is passed into
+this function, we need room on the stack to hold the 7 values which may be
returned.
We do this by using the PPCODE: directive, rather than the CODE: directive.
@@ -1133,7 +1125,7 @@ And add the following code to Mytest.t, while incrementing the "11"
tests to "13":
$results = Mytest::multi_statfs([ '/', '/blech' ]);
- ok( ref $results->[0]) );
+ ok( ref $results->[0] );
ok( ! ref $results->[1] );
=head2 New Things in this Example
@@ -1312,7 +1304,7 @@ layer. If it can't find one, it will call C<PerlIO_exportFILE()> to
generate a new stdio C<FILE>. Please only call C<PerlIO_exportFILE()> if
you want a I<new> C<FILE>. It will generate one on each call and push a
new stdio layer. So don't call it repeatedly on the same
-file. C<PerlIO()>_findFILE will retrieve the stdio layer once it has been
+file. C<PerlIO_findFILE()> will retrieve the stdio layer once it has been
generated by C<PerlIO_exportFILE()>.
This applies to the perlio system only. For versions before 5.7,