Skip to content

Commit

Permalink
fix broken usenet/email reply rendering in FAQ
Browse files Browse the repository at this point in the history
Like HTML or Markdown, POD does not preserve line breaks within a
paragraph, so all those ">" quoted reply lines come out looking broken.
Use a verbatim block instead.
  • Loading branch information
mauke committed Apr 8, 2024
1 parent 2810af6 commit 04367ee
Showing 1 changed file with 19 additions and 19 deletions.
38 changes: 19 additions & 19 deletions lib/Test/FAQ.pod
Original file line number Diff line number Diff line change
Expand Up @@ -212,12 +212,12 @@ C<ok(...) || diag "...";>

=head2 Why use an ok() function?

On Tue, Aug 28, 2001 at 02:12:46PM +0100, Robin Houston wrote:
> Michael Schwern wrote:
> > Ah HA! I've been wondering why nobody ever thinks to write a simple
> > ok() function for their tests! perlhack has bad testing advice.
>
> Could you explain the advantage of having a "simple ok() function"?
On Tue, Aug 28, 2001 at 02:12:46PM +0100, Robin Houston wrote:
> Michael Schwern wrote:
> > Ah HA! I've been wondering why nobody ever thinks to write a simple
> > ok() function for their tests! perlhack has bad testing advice.
>
> Could you explain the advantage of having a "simple ok() function"?

Because writing:

Expand All @@ -230,9 +230,9 @@ first place. It also looks like hell and obscures the real purpose.
Besides, that will cause problems on VMS.


> As somebody who has spent many painful hours debugging test failures,
> I'm intimately familiar with the _disadvantages_. When you run the
> test, you know that "test 113 failed". That's all you know, in general.
> As somebody who has spent many painful hours debugging test failures,
> I'm intimately familiar with the _disadvantages_. When you run the
> test, you know that "test 113 failed". That's all you know, in general.

Second advantage is you can easily upgrade the C<ok()> function to fix
this, either by slapping this line in:
Expand Down Expand Up @@ -333,16 +333,16 @@ The most useful functions in L<Test::More> are C<is()>, C<like()> and C<is_deepl

=head2 How do I check for an infinite loop?

On Mon, Mar 18, 2002 at 03:57:55AM -0500, Mark-Jason Dominus wrote:
>
> Michael The Schwern <schwern@pobox.com> says:
> > Use alarm and skip the test if $Config{d_alarm} is false (see
> > t/op/alarm.t for an example). If you think the infinite loop is due
> > to a programming glitch, as opposed to a cross-platform issue, this
> > will be enough.
>
> Thanks very much!
>
On Mon, Mar 18, 2002 at 03:57:55AM -0500, Mark-Jason Dominus wrote:
>
> Michael The Schwern <schwern@pobox.com> says:
> > Use alarm and skip the test if $Config{d_alarm} is false (see
> > t/op/alarm.t for an example). If you think the infinite loop is due
> > to a programming glitch, as opposed to a cross-platform issue, this
> > will be enough.
>
> Thanks very much!
>

=head2 How can I check that flock works?

Expand Down

0 comments on commit 04367ee

Please sign in to comment.