diff options
| author | Andy Lester <andy@petdance.com> | 2005-06-02 11:19:54 -0500 |
|---|---|---|
| committer | Rafael Garcia-Suarez <rgarciasuarez@gmail.com> | 2005-06-03 08:04:25 +0000 |
| commit | b432a67249666bce4aa3385263660dc667d150d7 (patch) | |
| tree | d7fccc07dbacb727f1e2d96499970be0b3682421 /pod/perlfaq8.pod | |
| parent | 3a205795a9fa8c21e484e9a8efe6e9257c24bd1e (diff) | |
| download | perl-b432a67249666bce4aa3385263660dc667d150d7.tar.gz | |
Quotes in pod/*.pod
Message-ID: <20050602211954.GA22107@petdance.com>
p4raw-id: //depot/perl@24686
Diffstat (limited to 'pod/perlfaq8.pod')
| -rw-r--r-- | pod/perlfaq8.pod | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/pod/perlfaq8.pod b/pod/perlfaq8.pod index 9648bff043..f0df9d3983 100644 --- a/pod/perlfaq8.pod +++ b/pod/perlfaq8.pod @@ -276,8 +276,8 @@ next. If you expect characters to get to your device when you print() them, you'll want to autoflush that filehandle. You can use select() and the C<$|> variable to control autoflushing (see L<perlvar/$E<verbar>> -and L<perlfunc/select>, or L<perlfaq5>, ``How do I flush/unbuffer an -output filehandle? Why must I do this?''): +and L<perlfunc/select>, or L<perlfaq5>, "How do I flush/unbuffer an +output filehandle? Why must I do this?"): $oldh = select(DEV); $| = 1; @@ -411,7 +411,7 @@ You don't actually "trap" a control character. Instead, that character generates a signal which is sent to your terminal's currently foregrounded process group, which you then trap in your process. Signals are documented in L<perlipc/"Signals"> and the -section on ``Signals'' in the Camel. +section on "Signals" in the Camel. You can set the values of the %SIG hash to be the functions you want to handle the signal. After perl catches the signal, it looks in %SIG @@ -527,7 +527,7 @@ though, so if you use END blocks you should also use Perl's exception-handling mechanism is its eval() operator. You can use eval() as setjmp and die() as longjmp. For details of this, see the section on signals, especially the time-out handler for a blocking -flock() in L<perlipc/"Signals"> or the section on ``Signals'' in +flock() in L<perlipc/"Signals"> or the section on "Signals" in the Camel Book. If exception handling is all you're interested in, try the @@ -1017,7 +1017,7 @@ the current process group of your controlling terminal as follows: Use the alarm() function, probably in conjunction with a signal handler, as documented in L<perlipc/"Signals"> and the section on -``Signals'' in the Camel. You may instead use the more flexible +"Signals" in the Camel. You may instead use the more flexible Sys::AlarmCall module available from CPAN. The alarm() function is not implemented on all versions of Windows. @@ -1177,8 +1177,8 @@ just need to replace step 3 (B<make>) with B<make perl> and you will get a new F<perl> binary with your extension linked in. See L<ExtUtils::MakeMaker> for more details on building extensions. -See also the next question, ``What's the difference between require -and use?''. +See also the next question, "What's the difference between require +and use?". =head2 What's the difference between require and use? |