TAP::Parser::ResultFactory(3p)

TAP::Parser::ResultFactory3p

Factory for creating tap::parser output objects

Usage

  use TAP::Parser::ResultFactory;
  my $token   = {...};
  my $factory = TAP::Parser::ResultFactory->new;
  my $result  = $factory->make_result( $token );

Version

Version 3.50

Description

This is a simple factory class which returns a TAP::Parser::Result subclass representing the current bit of test data from TAP (usually a single line). It is used primarily by TAP::Parser::Grammar. Unless you're subclassing, you probably won't need to use this module directly.

Methods

Class Methods

"new"

Creates a new factory class. Note: You currently don't need to instantiate a factory in order to use it.

"make_result"

Returns an instance the appropriate class for the test token passed in.

  my $result = TAP::Parser::ResultFactory->make_result($token);

Can also be called as an instance method.

"class_for"

Takes one argument: $type. Returns the class for this $type, or "croak"s with an error.

"register_type"

Takes two arguments: $type, $class

This lets you override an existing type with your own custom type, or register a completely new type, eg:

  # create a custom result type:
  package MyResult;
  use strict;
  use base 'TAP::Parser::Result';
  # register with the factory:
  TAP::Parser::ResultFactory->register_type( 'my_type' => __PACKAGE__ );
  # use it:
  my $r = TAP::Parser::ResultFactory->( { type => 'my_type' } );

Your custom type should then be picked up automatically by the TAP::Parser.

Subclassing

Please see "SUBCLASSING" in TAP::Parser for a subclassing overview.

There are a few things to bear in mind when creating your own "ResultFactory":

1.

The factory itself is never instantiated (this may change in the future). This means that "_initialize" is never called.

2.

"TAP::Parser::Result->new" is never called, $tokens are reblessed. This will change in a future version!

3.

TAP::Parser::Result subclasses will register themselves with TAP::Parser::ResultFactory directly:

  package MyFooResult;
  TAP::Parser::ResultFactory->register_type( foo => __PACKAGE__ );

Of course, it's up to you to decide whether or not to ignore them.

Example

  package MyResultFactory;
  use strict;
  use MyResult;
  use base 'TAP::Parser::ResultFactory';
  # force all results to be 'MyResult'
  sub class_for {
    return 'MyResult';
  }
  1;

Releases

32 releases since OpenBSD 5.0; the text changed 20 times.

  1. 5.0–5.3
  2. 5.4–5.5
  3. 5.6
  4. 5.7
  5. 5.8–5.9
  6. 6.0
  7. 6.1
  8. 6.2
  9. 6.3–6.4
  10. 6.5
  11. 6.6
  12. 6.7
  13. 6.8
  14. 6.9–7.2
  15. 7.3
  16. 7.4
  17. 7.5
  18. 7.6
  19. 7.7–7.8
  20. 7.9
  21. 8.0

From man 8.0-current-20261101 in OpenBSD 8.0-current (2026-11-01). Parsed by carta from the page's man source.