TAP::Pa...Factory(3pm)

🌸 NAME 🌸

okay so welcome to the TAP::Parser::ResultFactory page from the Perl Programmers Reference Guide, bestie β€” it's the TAP::Parser::ResultFactory (3pm) manual, and it's literally the Factory for creating TAP::Parser output objects. πŸ’…

✨ SYNOPSIS ✨

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

🏷️ VERSION 🏷️

Version 3.50 β€” slay. πŸ’–

πŸŽ€ DESCRIPTION πŸŽ€

This is a simple factory class that returns a TAP::Parser::Result subclass representing the current bit of test data from TAP (usually a single line). It's used primarily by TAP::Parser::Grammar. And ngl, unless you're subclassing, you probably won't need to use this module directly β€” it's giving "behind the scenes main character energy." πŸ¦‹

πŸ› οΈ METHODS πŸ› οΈ

🧸 Class Methods 🧸

✨ new ✨

Creates a new factory class. Note: you currently don't need to instantiate a factory in order to use it. No cap. πŸ’…

πŸ’– make_result πŸ’–

Returns an instance of 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. Iconic. ✨

πŸ”₯ class_for πŸ”₯

Takes one argument: $type. Returns the class for this $type, or croaks 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. Big "it just works" vibes. 🌈

🌟 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. Lowkey your call, bestie. πŸ™ˆ

🌈 Example 🌈

package MyResultFactory;

use strict;

use MyResult;

use base 'TAP::Parser::ResultFactory';

# force all results to be 'MyResult'
sub class_for {
  return 'MyResult';
}

1;

πŸ‘€ SEE ALSO πŸ‘€

  • TAP::Parser
  • TAP::Parser::Result
  • TAP::Parser::Grammar

okay that's the whole page, bestie πŸ’– cute sign-off: this is from perl v5.42.3, dated 2026-11-03, and it's the TAP::Pa...Factory(3pm) manual-footer vibe. mwah 🫢

πŸ“¦ where this page comes from