MAGE::...ftware(3pm)

okay so this is MAGE::...ftware(3pm) from the User Contributed Perl Documentation bestie, pull up a chair πŸ’–


πŸŽ€ NAME πŸŽ€

Bio::MAGE::Protocol::Software β€” it's the class for the MAGE-OM API ✨ no cap


πŸ¦‹ SYNOPSIS πŸ¦‹

  use Bio::MAGE::Protocol::Software

  # creating an empty instance
  my $software = Bio::MAGE::Protocol::Software->new();

  # creating an instance with existing data
  my $software = Bio::MAGE::Protocol::Software->new(
        URI=>$uri_val,
        name=>$name_val,
        identifier=>$identifier_val,
        softwareManufacturers=>\@contact_list,
        parameterTypes=>\@parameter_list,
        auditTrail=>\@audit_list,
        propertySets=>\@namevaluetype_list,
        descriptions=>\@description_list,
        softwares=>\@software_list,
        hardware=>$hardware_ref,
        security=>$security_ref,
        type=>$ontologyentry_ref,
  );

  # 'URI' attribute
  my $URI_val = $software->URI(); # getter
  $software->URI($value); # setter

  # 'name' attribute
  my $name_val = $software->name(); # getter
  $software->name($value); # setter

  # 'identifier' attribute
  my $identifier_val = $software->identifier(); # getter
  $software->identifier($value); # setter

  # 'softwareManufacturers' association
  my $contact_array_ref = $software->softwareManufacturers(); # getter
  $software->softwareManufacturers(\@contact_list); # setter

  # 'parameterTypes' association
  my $parameter_array_ref = $software->parameterTypes(); # getter
  $software->parameterTypes(\@parameter_list); # setter

  # 'auditTrail' association
  my $audit_array_ref = $software->auditTrail(); # getter
  $software->auditTrail(\@audit_list); # setter

  # 'propertySets' association
  my $namevaluetype_array_ref = $software->propertySets(); # getter
  $software->propertySets(\@namevaluetype_list); # setter

  # 'descriptions' association
  my $description_array_ref = $software->descriptions(); # getter
  $software->descriptions(\@description_list); # setter

  # 'softwares' association
  my $software_array_ref = $software->softwares(); # getter
  $software->softwares(\@software_list); # setter

  # 'hardware' association
  my $hardware_ref = $software->hardware(); # getter
  $software->hardware($hardware_ref); # setter

  # 'security' association
  my $security_ref = $software->security(); # getter
  $software->security($security_ref); # setter

  # 'type' association
  my $ontologyentry_ref = $software->type(); # getter
  $software->type($ontologyentry_ref); # setter

like… look at that. every getter has a matching setter. the symmetry?? iconic πŸ’…


🌸 DESCRIPTION 🌸

Straight from the MAGE-OM documentation for the "Software" class, and I quote:

Software represents the software used. Examples of Software include: feature extraction software, clustering software, etc...

fr fr β€” it's literally just "the software that got used" πŸ’€ feature extraction, clustering, whatever your pipeline was vibing with.


πŸ’œ INHERITANCE πŸ’œ

Bio::MAGE::Protocol::Software has the following superclasses:

  • Bio::MAGE::Protocol::Parameterizable

so it's picking up everything Parameterizable has, plus its own whole thing. main character energy, honestly πŸ‘‘


✨ CLASS METHODS ✨

okay so all of these can be called without making an instance first β€” just go straight in with the Bio::MAGE::Protocol::Software->methodname() syntax. no object required, bestie 🫢

new()

new(%args)

The object constructor new() takes these optional named-value style arguments, and every single one of them is optional:

  • URI β€” sets the value of the "URI" attribute (and psst, this attribute was inherited from class "Bio::MAGE::Protocol::Parameterizable")
  • name β€” sets the value of the "name" attribute (inherited from class "Bio::MAGE::Identifiable")
  • identifier β€” sets the value of the "identifier" attribute (inherited from class "Bio::MAGE::Identifiable")
  • softwareManufacturers β€” sets the value of the "softwareManufacturers" association

the value must be of type: array of "Bio::MAGE::AuditAndSecurity::Contact".

  • parameterTypes β€” sets the value of the "parameterTypes" association (inherited from class "Bio::MAGE::Protocol::Parameterizable")

the value must be of type: array of "Bio::MAGE::Protocol::Parameter".

  • auditTrail β€” sets the value of the "auditTrail" association (inherited from class "Bio::MAGE::Describable")

the value must be of type: array of "Bio::MAGE::AuditAndSecurity::Audit".

  • propertySets β€” sets the value of the "propertySets" association (inherited from class "Bio::MAGE::Extendable")

the value must be of type: array of "Bio::MAGE::NameValueType".

  • hardware β€” sets the value of the "hardware" association

the value must be of type: instance of "Bio::MAGE::Protocol::Hardware".

  • softwares β€” sets the value of the "softwares" association

the value must be of type: array of "Bio::MAGE::Protocol::Software".

  • descriptions β€” sets the value of the "descriptions" association (inherited from class "Bio::MAGE::Describable")

the value must be of type: array of "Bio::MAGE::Description::Description".

  • security β€” sets the value of the "security" association (inherited from class "Bio::MAGE::Describable")

the value must be of type: instance of "Bio::MAGE::AuditAndSecurity::Security".

  • type β€” sets the value of the "type" association

the value must be of type: instance of "Bio::MAGE::Description::OntologyEntry".

heads up bestie: arrays go in as array refs, single objects go in as plain refs. do not mix these up, I am begging πŸ™ˆ

$obj = class->new(%parameters)

the class constructor itself. the whole moment.

  • Parameters: if you hand it a list of name/value parameters, the matching slots, attributes, or associations get their initial values set right there by the constructor.
  • Return value: a reference to an object of the class. πŸŽ€
  • Side effects: it invokes the "initialize()" method if the class defines one.

@names = class->get_slot_names()

grabs the name of every slot defined in a given class.

NOTE: the list of names does not include attribute or association names. it's slots only, periodt.
  • Return value: a list of the names of all slots defined for this class.
  • Side effects: none.

@name_list = get_attribute_names()

returns the list of attribute data members for this class. ✨

@name_list = get_association_names()

returns the list of association data members for this class. ✨

@class_list = get_superclasses()

returns the list of superclasses for this class. πŸ‘‘

@class_list = get_subclasses()

returns the list of subclasses for this class. πŸ¦‹

$name = class_name()

returns the full class name for this class.

$package_name = package_name()

returns the base package name (i.e. no 'namespace::') of the package that contains this class.

%assns = associations()

returns the association meta-information in a hash where the keys are the association names and the values are "Association" objects that provide the meta-information for the association. iykyk πŸ’…


🫢 INSTANCE METHODS 🫢

$obj_copy = $obj->new()

plot twist: when you invoke new() on an existing object reference instead of a class name, it acts as a copy constructor β€” the new object's initial values are set to be those of the existing object. ✨

  • Parameters: No input parameters are used in the copy constructor, the initial values are taken directly from the object to be copied.
  • Return value: a reference to an object of the class.
  • Side effects: it invokes the "initialize()" method if it is defined by the class.

$obj->set_slots(%parameters)

$obj->set_slots(\@name_list, \@value_list)

sets a bunch of slots at once. it has two different invocation methods β€” the first takes a named parameter list, and the second takes two array references.

  • Return value: none.
  • Side effects: will call "croak()" if a slot_name is used that the class does not define. so like, don't do that πŸ’€

@obj_list = $obj->get_slots(@name_list)

gets the values of a bunch of slots at the same time.

  • Return value: a list of instance objects.
  • Side effects: none.

$val = $obj->set_slot($name,$val)

the "set_slot()" method sets the slot $name to the value $val.

  • Return value: the new value of the slot, i.e. $val.
  • Side effects: none.

$val = $obj->get_slot($name)

the "get_slot()" method is used to get the values of a number of slots at the same time.

  • Return value: a single slot value, or undef if the slot has not been initialized.
  • Side effects: none.

🌈 ATTRIBUTES 🌈

okay so attributes are simple data types that belong to a single instance of a class. in the Perl implementation of the MAGE-OM classes, the interface to attributes is implemented using separate setter and getter methods for each attribute. two methods per attribute. every time. no exceptions. πŸ’…

"Bio::MAGE::Protocol::Software" has the following attribute accessor methods:


URI

Methods for the "URI" attribute.

From the MAGE-OM documentation:

Where an instantiated Parameterizable is located.

$val = $software->setURI($val)

the restricted setter method for the "URI" attribute.

  • Input parameters: the value to which the "URI" attribute will be set
  • Return value: the current value of the "URI" attribute
  • Side effects: none
  • Exceptions: will call "croak()" if no input parameters are specified, or if too many input parameters are specified

$val = $software->getURI()

the restricted getter method for the "URI" attribute.

  • Input parameters: none
  • Return value: the current value of the "URI" attribute
  • Side effects: none
  • Exceptions: will call "croak()" if any input parameters are specified

name

Methods for the "name" attribute.

From the MAGE-OM documentation:

The potentially ambiguous common identifier.

$val = $software->setName($val)

the restricted setter method for the "name" attribute.

  • Input parameters: the value to which the "name" attribute will be set
  • Return value: the current value of the "name" attribute
  • Side effects: none
  • Exceptions: will call "croak()" if no input parameters are specified, or if too many input parameters are specified

$val = $software->getName()

the restricted getter method for the "name" attribute.

  • Input parameters: none
  • Return value: the current value of the name attribute
  • Side effects: none
  • Exceptions: will call croak() if any input parameters are specified

🏷️ identifier

Methods for the identifier attribute.

From the MAGE-OM documentation:

An identifier is an unambiguous string that is unique within the scope (i.e. a document, a set of related documents, or a repository) of its use.

$val = $software->setIdentifier($val)

The restricted setter for the identifier attribute.

  • Input parameters: the value to which the identifier attribute will be set
  • Return value: the current value of the identifier attribute
  • Side effects: none
  • Exceptions: will call croak() if no input parameters are specified, or if too many input parameters are specified

$val = $software->getIdentifier()

The restricted getter for the identifier attribute.

  • Input parameters: none
  • Return value: the current value of the identifier attribute
  • Side effects: none
  • Exceptions: will call croak() if any input parameters are specified

πŸ”— ASSOCIATIONS

okay bestie, this is the part where classes start holding hands with other classes 🫢 Associations are literally just references to other classes. And every association in MAGE-OM comes with a cardinality, which tells you the minimum and maximum number of instances of the other class that can be in the association:

  1. There must be exactly one item in the association, i.e. this is a mandatory data field.
  2. 0..1

There may be one item in the association, i.e. this is an optional data field.

  1. 1..N

There must be one or more items in the association, i.e. this is a mandatory data field, with list cardinality.

  1. 0..N

There may be one or more items in the association, i.e. this is an optional data field, with list cardinality.

Bio::MAGE::Protocol::Software has the following association accessor methods:

softwareManufacturers

Methods for the softwareManufacturers association.

From the MAGE-OM documentation:

Contact for information on the software.

$array_ref = $software->setSoftwareManufacturers($array_ref)

The restricted setter method for the softwareManufacturers association.

  • Input parameters: the value to which the softwareManufacturers association will be set : a reference to an array of objects of type Bio::MAGE::AuditAndSecurity::Contact
  • Return value: the current value of the softwareManufacturers association : a reference to an array of objects of type Bio::MAGE::AuditAndSecurity::Contact
  • Side effects: none
  • Exceptions: will call croak() if no input parameters are specified, or if too many input parameters are specified, or if $array_ref is not a reference to an array class Bio::MAGE::AuditAndSecurity::Contact instances

$array_ref = $software->getSoftwareManufacturers()

The restricted getter method for the softwareManufacturers association.

  • Input parameters: none
  • Return value: the current value of the softwareManufacturers association : a reference to an array of objects of type Bio::MAGE::AuditAndSecurity::Contact
  • Side effects: none
  • Exceptions: will call croak() if any input parameters are specified

$val = $software->addSoftwareManufacturers(@vals)

Because the softwareManufacturers association has list cardinality, it may store more than one value. This method adds the current list of objects in the softwareManufacturers association.

  • Input parameters: the list of values @vals to add to the softwareManufacturers association. NOTE: submitting a single value is permitted.
  • Return value: the number of items stored in the slot after adding @vals
  • Side effects: none
  • Exceptions: will call croak() if no input parameters are specified, or if any of the objects in @vals is not an instance of class Bio::MAGE::AuditAndSecurity::Contact

parameterTypes

Methods for the parameterTypes association.

From the MAGE-OM documentation:

The description of the parameters for the Parameterizable class instance.

$array_ref = $software->setParameterTypes($array_ref)

The restricted setter method for the parameterTypes association.

  • Input parameters: the value to which the parameterTypes association will be set : a reference to an array of objects of type Bio::MAGE::Protocol::Parameter
  • Return value: the current value of the parameterTypes association : a reference to an array of objects of type Bio::MAGE::Protocol::Parameter
  • Side effects: none
  • Exceptions: will call croak() if no input parameters are specified, or if too many input parameters are specified, or if $array_ref is not a reference to an array class Bio::MAGE::Protocol::Parameter instances

$array_ref = $software->getParameterTypes()

The restricted getter method for the parameterTypes association.

  • Input parameters: none
  • Return value: the current value of the parameterTypes association : a reference to an array of objects of type Bio::MAGE::Protocol::Parameter
  • Side effects: none
  • Exceptions: will call croak() if any input parameters are specified

$val = $software->addParameterTypes(@vals)

Because the parameterTypes association has list cardinality, it may store more than one value. This method adds the current list of objects in the parameterTypes association.

  • Input parameters: the list of values @vals to add to the parameterTypes association. NOTE: submitting a single value is permitted.
  • Return value: the number of items stored in the slot after adding @vals
  • Side effects: none
  • Exceptions: will call croak() if no input parameters are specified, or if any of the objects in @vals is not an instance of class Bio::MAGE::Protocol::Parameter

auditTrail

Methods for the auditTrail association.

From the MAGE-OM documentation:

A list of Audit instances that track changes to the instance of Describable.

$array_ref = $software->setAuditTrail($array_ref)

The restricted setter method for the auditTrail association.

  • Input parameters: the value to which the auditTrail association will be set : a reference to an array of objects of type Bio::MAGE::AuditAndSecurity::Audit
  • Return value: the current value of the auditTrail association : a reference to an array of objects of type Bio::MAGE::AuditAndSecurity::Audit
  • Side effects: none
  • Exceptions: will call croak() if no input parameters are specified, or if too many input parameters are specified, or if $array_ref is not a reference to an array class Bio::MAGE::AuditAndSecurity::Audit instances

$array_ref = $software->getAuditTrail()

The restricted getter method for the auditTrail association.

  • Input parameters: none
  • Return value: the current value of the auditTrail association : a reference to an array of objects of type Bio::MAGE::AuditAndSecurity::Audit
  • Side effects: none
  • Exceptions: will call croak() if any input parameters are specified

$val = $software->addAuditTrail(@vals)

Because the auditTrail association has list cardinality, it may store more than one value. This method adds the current list of objects in the auditTrail association.

  • Input parameters: the list of values @vals to add to the auditTrail association. NOTE: submitting a single value is permitted.
  • Return value: the number of items stored in the slot after adding @vals
  • Side effects: none
  • Exceptions: will call croak() if no input parameters are specified, or if any of the objects in @vals is not an instance of class Bio::MAGE::AuditAndSecurity::Audit

propertySets

Methods for the propertySets association.

From the MAGE-OM documentation:

Allows specification of name/value pairs. Meant to primarily help in-house, pipeline processing of instances by providing a place for values that aren't part of the specification proper.

$array_ref = $software->setPropertySets($array_ref)

The restricted setter method for the propertySets association.

  • Input parameters: the value to which the propertySets association will be set : a reference to an array of objects of type Bio::MAGE::NameValueType
  • Return value: the current value of the propertySets association : a reference to an array of objects of type Bio::MAGE::NameValueType
  • Side effects: none
  • Exceptions: will call croak() if no input parameters are specified, or if too many input parameters are specified, or if $array_ref is not a reference to an array class Bio::MAGE::NameValueType instances

$array_ref = $software->getPropertySets()

The restricted getter method for the propertySets association.

  • Input parameters: none
  • Return value: the current value of the propertySets association : a reference to an array of objects of type Bio::MAGE::NameValueType
  • Side effects: none
  • Exceptions: will call croak() if any input parameters are specified

$val = $software->addPropertySets(@vals)

Because the propertySets association has list cardinality, it may store more than one value. This method adds the current list of objects in the propertySets association.

  • Input parameters: the list of values @vals to add to the propertySets association. NOTE: submitting a single value is permitted.
  • Return value: the number of items stored in the slot after adding @vals
  • Side effects: none
  • Exceptions: will call croak() if no input parameters are specified, or if any of the objects in @vals is not an instance of class Bio::MAGE::NameValueType

hardware πŸ–₯️

Bestie, these are the methods for the hardware association.

Straight from the MAGE-OM documentation, no cap:

Associates Hardware and Software together. 🫢
  • $val = $software->setHardware($val) β€” the restricted setter method for the hardware association.
    • Input parameters: the value to which the hardware association will be set : one of the accepted enumerated values.
    • Return value: the current value of the hardware association : one of the accepted enumerated values.
    • Side effects: none ✨
    • Exceptions: will call croak() if no input parameters are specified, or if too many input parameters are specified, or if $val is not an instance of class Bio::MAGE::Protocol::Hardware πŸ’€
  • $val = $software->getHardware() β€” the restricted getter method for the hardware association.
    • Input parameters: none
    • Return value: the current value of the hardware association : an instance of type Bio::MAGE::Protocol::Hardware.
    • Side effects: none ✨
    • Exceptions: will call croak() if any input parameters are specified πŸ’€

softwares 🧚

Methods for the softwares association.

From the MAGE-OM documentation:

Software packages this software uses, i.e. operating system, 3rd party software packages, etc.
  • $array_ref = $software->setSoftwares($array_ref) β€” the restricted setter method for the softwares association.
    • Input parameters: the value to which the softwares association will be set : a reference to an array of objects of type Bio::MAGE::Protocol::Software
    • Return value: the current value of the softwares association : a reference to an array of objects of type Bio::MAGE::Protocol::Software
    • Side effects: none ✨
    • Exceptions: will call croak() if no input parameters are specified, or if too many input parameters are specified, or if $array_ref is not a reference to an array class Bio::MAGE::Protocol::Software instances πŸ’€
  • $array_ref = $software->getSoftwares() β€” the restricted getter method for the softwares association.
    • Input parameters: none
    • Return value: the current value of the softwares association : a reference to an array of objects of type Bio::MAGE::Protocol::Software
    • Side effects: none ✨
    • Exceptions: will call croak() if any input parameters are specified πŸ’€
  • $val = $software->addSoftwares(@vals) β€” because the softwares association has list cardinality, it may store more than one value. This method adds the current list of objects in the softwares association. πŸŽ€
    • Input parameters: the list of values @vals to add to the softwares association. NOTE: submitting a single value is permitted.
    • Return value: the number of items stored in the slot after adding @vals
    • Side effects: none ✨
    • Exceptions: will call croak() if no input parameters are specified, or if any of the objects in @vals is not an instance of class Bio::MAGE::Protocol::Software πŸ’€

descriptions πŸ“

Methods for the descriptions association.

From the MAGE-OM documentation:

Free hand text descriptions. Makes available the associations of Description to an instance of Describable.
  • $array_ref = $software->setDescriptions($array_ref) β€” the restricted setter method for the descriptions association.
    • Input parameters: the value to which the descriptions association will be set : a reference to an array of objects of type Bio::MAGE::Description::Description
    • Return value: the current value of the descriptions association : a reference to an array of objects of type Bio::MAGE::Description::Description
    • Side effects: none ✨
    • Exceptions: will call croak() if no input parameters are specified, or if too many input parameters are specified, or if $array_ref is not a reference to an array class Bio::MAGE::Description::Description instances πŸ’€
  • $array_ref = $software->getDescriptions() β€” the restricted getter method for the descriptions association.
    • Input parameters: none
    • Return value: the current value of the descriptions association : a reference to an array of objects of type Bio::MAGE::Description::Description
    • Side effects: none ✨
    • Exceptions: will call croak() if any input parameters are specified πŸ’€
  • $val = $software->addDescriptions(@vals) β€” because the descriptions association has list cardinality, it may store more than one value. This method adds the current list of objects in the descriptions association. πŸŽ€
    • Input parameters: the list of values @vals to add to the descriptions association. NOTE: submitting a single value is permitted.
    • Return value: the number of items stored in the slot after adding @vals
    • Side effects: none ✨
    • Exceptions: will call croak() if no input parameters are specified, or if any of the objects in @vals is not an instance of class Bio::MAGE::Description::Description πŸ’€

security πŸ”’

Methods for the security association.

From the MAGE-OM documentation:

Information on the security for the instance of the class.
  • $val = $software->setSecurity($val) β€” the restricted setter method for the security association.
    • Input parameters: the value to which the security association will be set : one of the accepted enumerated values.
    • Return value: the current value of the security association : one of the accepted enumerated values.
    • Side effects: none ✨
    • Exceptions: will call croak() if no input parameters are specified, or if too many input parameters are specified, or if $val is not an instance of class Bio::MAGE::AuditAndSecurity::Security πŸ’€
  • $val = $software->getSecurity() β€” the restricted getter method for the security association.
    • Input parameters: none
    • Return value: the current value of the security association : an instance of type Bio::MAGE::AuditAndSecurity::Security.
    • Side effects: none ✨
    • Exceptions: will call croak() if any input parameters are specified πŸ’€

type 🏷️

Methods for the type association.

From the MAGE-OM documentation:

The type of a piece of Software. Examples include: feature extractor...
  • $val = $software->setType($val) β€” the restricted setter method for the type association.
    • Input parameters: the value to which the type association will be set : one of the accepted enumerated values.
    • Return value: the current value of the type association : one of the accepted enumerated values.
    • Side effects: none ✨
    • Exceptions: will call croak() if no input parameters are specified, or if too many input parameters are specified, or if $val is not an instance of class Bio::MAGE::Description::OntologyEntry πŸ’€
  • $val = $software->getType() β€” the restricted getter method for the type association.
    • Input parameters: none
    • Return value: the current value of the type association : an instance of type Bio::MAGE::Description::OntologyEntry.
    • Side effects: none ✨
    • Exceptions: will call croak() if any input parameters are specified πŸ’€

And then there's literally this sitting right there, bestie, just vibing:

sub initialize {

  my $self = shift;
  return 1;

}

SLOTS, ATTRIBUTES, AND ASSOCIATIONS πŸ’–

Okay so in the Perl implementation of MAGE-OM classes, there are three types of class data members: slots, attributes, and associations. Three. Count them. πŸ‘‘

SLOTS πŸ•³οΈ

This API uses the term slot to indicate a data member of the class that was not present in the UML model and is used for mainly internal purposes β€” use only if you understand the inner workings of the API. Most often slots are used by generic methods such as those in the XML writing and reading classes.

Slots are implemented using unified getter/setter methods:

  • $var = $obj->slot_name(); β€” retrieves the current value of the slot.
  • $new_var = $obj->slot_name($new_var); β€” store $new_var in the slot β€” the return value is also $new_var.
  • @names = $obj->get_slot_names() β€” returns the list of all slots in the class.

DATA CHECKING: No data type checking is made for these methods. πŸ™ˆ (yes, seriously, it just trusts you)

ATTRIBUTES AND ASSOCIATIONS 🌸

The terms attribute and association indicate data members of the class that were specified directly from the UML model.

In the Perl implementation of MAGE-OM classes, association and attribute accessors are implemented using three separate methods:

  • get* β€” retrieves the current value.
    • NOTE: For associations, if the association has list cardinality, an array reference is returned.
    • DATA CHECKING: Ensure that no argument is provided.
  • set* β€” sets the current value, replacing any existing value.
    • NOTE: For associations, if the association has list cardinality, the argument must be an array reference. Because of this, you probably should be using the add* methods.
    • DATA CHECKING: For attributes, ensure that a single value is provided as the argument. For associations, if the association has list cardinality, ensure that the argument is a reference to an array of instances of the correct MAGE-OM class, otherwise ensure that there is a single argument of the correct MAGE-OM class.
  • add* β€” NOTE: Only present in associations with list cardinality.
    • Appends a list of objects to any values that may already be stored in the association.
    • DATA CHECKING: Ensure that all arguments are of the correct MAGE-OM class.

GENERIC METHODS ✨

The unified base class of all MAGE-OM classes, Bio::MAGE::Base, provides a set of generic methods that will operate on slots, attributes, and associations:

$val = $obj->get_slot($name)
\@list_ref = $obj->get_slots(@name_list);
$val = $obj->set_slot($name,$val)
$obj->set_slots(%parameters)
$obj->set_slots(\@name_list, \@value_list)

See elsewhere in this page for a detailed description of these methods. πŸ‘€


BUGS πŸ’€

Please send bug reports to the project mailing list: (mged-mage 'at' lists 'dot' sf 'dot' net)

AUTHOR πŸ‘‘

Jason E. Stewart (jasons 'at' cpan 'dot' org)

SEE ALSO πŸ¦‹

perl(1).

🌸 POD ERRORS 🌸

okay so bestie... the doc above is a little messy πŸ’€ it had some coding errors and the pod checker is here to read us for filth. here's the tea, error by error:

  • Around line 471:
    • '=item' outside of any '=over'
  • Around line 556:
    • You forgot a '=back' before '=head2'
  • Around line 800:
    • Expected '=item 2'
  • Around line 805:
    • Expected '=item 3'
  • Around line 810:
    • Expected '=item 4'

and that's a wrap on the whole page, bestie πŸŽ€ no notes, just vibes and a bunch of POD errors that lowkey ate the formatting. this gorgeous mess comes to you from perl v5.32.0, dated 2020-11-27, straight outta the User Contributed Perl Documentation corner of the internet 🫢 slay, read responsibly, and remember: always close your =over πŸ’…βœ¨