MAGE::...eporter(3pm)

📦 version 20030502.3, in debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu resolute, ubuntu stonking

🌸 NAME 🌸

Okay so bestie, this is the manual page MAGE::...eporter(3pm) from User Contributed Perl Documentation, and it's all about Bio::MAGE::DesignElement::Reporter — Class for the MAGE-OM API. That's the whole name vibe. Periodt. 💅

✨ SYNOPSIS ✨

Here's how you bring this class into your life, fr fr:

use Bio::MAGE::DesignElement::Reporter

# creating an empty instance
my $reporter = Bio::MAGE::DesignElement::Reporter->new();

# creating an instance with existing data
my $reporter = Bio::MAGE::DesignElement::Reporter->new(
      name=>$name_val,
      identifier=>$identifier_val,
      controlType=>$ontologyentry_ref,
      auditTrail=>\@audit_list,
      propertySets=>\@namevaluetype_list,
      warningType=>$ontologyentry_ref,
      failTypes=>\@ontologyentry_list,
      descriptions=>\@description_list,
      security=>$security_ref,
      immobilizedCharacteristics=>\@biosequence_list,
      featureReporterMaps=>\@featurereportermap_list,
);

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

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

# 'controlType' association
my $ontologyentry_ref = $reporter->controlType(); # getter
$reporter->controlType($ontologyentry_ref); # setter

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

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

# 'warningType' association
my $ontologyentry_ref = $reporter->warningType(); # getter
$reporter->warningType($ontologyentry_ref); # setter

# 'failTypes' association
my $ontologyentry_array_ref = $reporter->failTypes(); # getter
$reporter->failTypes(\@ontologyentry_list); # setter

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

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

# 'immobilizedCharacteristics' association
my $biosequence_array_ref = $reporter->immobilizedCharacteristics(); # getter
$reporter->immobilizedCharacteristics(\@biosequence_list); # setter

# 'featureReporterMaps' association
my $featurereportermap_array_ref = $reporter->featureReporterMaps(); # getter
$reporter->featureReporterMaps(\@featurereportermap_list); # setter

💖 DESCRIPTION 💖

From the MAGE-OM documentation for the "Reporter" class, okay so listen:

A Design Element that represents some biological material (clone, oligo, etc.) on an array which will report on some biosequence or biosequences. The derived data from the measured data of its Features represents the presence or absence of the biosequence or biosequences it is reporting on in the BioAssay.

Reporters are Identifiable and several Features on the same array can be mapped to the same reporter as can Features from a different ArrayDesign. The granularity of the Reporters independence is dependent on the technology and the intent of the ArrayDesign. Oligos using mature technologies can in general be assumed to be safely replicated on many features where as with PCR Products there might be the desire for quality assurence to make reporters one to one with features and use the mappings to CompositeSequences for replication purposes.

That's the whole lore. No cap. 🧬✨

👑 INHERITANCE 👑

Bio::MAGE::DesignElement::Reporter has the following superclasses:

  • Bio::MAGE::DesignElement::DesignElement

🌈 CLASS METHODS 🌈

The following methods can all be called without first having an instance of the class via the Bio::MAGE::DesignElement::Reporter->methodname() syntax. It's giving class-level main character energy. 💅

new()

new(%args)

The object constructor new() accepts the following optional named-value style arguments:

  • name — Sets the value of the name attribute (this attribute was inherited from class Bio::MAGE::Identifiable).
  • identifier — Sets the value of the identifier attribute (this attribute was inherited from class Bio::MAGE::Identifiable).
  • controlType — Sets the value of the controlType association (this association was inherited from class Bio::MAGE::DesignElement::DesignElement). The value must be of type: instance of Bio::MAGE::Description::OntologyEntry.
  • auditTrail — Sets the value of the auditTrail association (this association was 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 (this association was inherited from class Bio::MAGE::Extendable). The value must be of type: array of Bio::MAGE::NameValueType.
  • warningType — Sets the value of the warningType association. The value must be of type: instance of Bio::MAGE::Description::OntologyEntry.
  • failTypes — Sets the value of the failTypes association. The value must be of type: array of Bio::MAGE::Description::OntologyEntry.
  • descriptions — Sets the value of the descriptions association (this association was 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 (this association was inherited from class Bio::MAGE::Describable). The value must be of type: instance of Bio::MAGE::AuditAndSecurity::Security.
  • immobilizedCharacteristics — Sets the value of the immobilizedCharacteristics association. The value must be of type: array of Bio::MAGE::BioSequence::BioSequence.
  • featureReporterMaps — Sets the value of the featureReporterMaps association. The value must be of type: array of Bio::MAGE::DesignElement::FeatureReporterMap.

$obj = class->new(%parameters)

The new() method is the class constructor.

Parameters: if given a list of name/value parameters the corresponding slots, attributes, or associations will have their initial values set by the constructor.

Return value: It returns a reference to an object of the class.

Side effects: It invokes the initialize() method if it is defined by the class.

@names = class->get_slot_names()

The get_slot_names() method is used to retrieve the name of all slots defined in a given class.

NOTE: the list of names does not include attribute or association names.

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.

🦋 INSTANCE METHODS 🦋

$obj_copy = $obj->new()

When invoked with an existing object reference and not a class name, the new() method acts as a copy constructor — with the new object's initial values 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: It returns 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)

The set_slots() method is used to set a number of slots at the same time. 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.

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

The get_slots() method is used to get the values of a number 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

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.

Bio::MAGE::DesignElement::Reporter has the following attribute accessor methods:

name

Methods for the name attribute.

From the MAGE-OM documentation:

The potentially ambiguous common identifier.

$val = $reporter->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 = $reporter->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.

Straight from the MAGE-OM documentation, bestie, and I quote:

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 = $reporter->setIdentifier($val)

The restricted setter for the "identifier" attribute. 💅

  • Input parameters: the value you wanna set the "identifier" attribute to
  • Return value: whatever the "identifier" attribute currently is
  • Side effects: none, she's chill
  • Exceptions: will call croak() if you pass no input parameters, or if you pass too many input parameters 🙈

$val = $reporter->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 you pass any input parameters 😭

✨ ASSOCIATIONS ✨

Okay so associations are just references to other classes 🫶. And in MAGE-OM, every association has a cardinality — that's the thing that tells you the minimum and maximum number of instances of the 'other' class that can be in the association. Vibe check time:

  1. 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.
  3. 1..N — There must be one or more items in the association, i.e. this is a mandatory data field, with list cardinality.
  4. 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::DesignElement::Reporter has the following association accessor methods, and yes we're going through every single one, no skipping 💀:

controlType

Methods for the "controlType" association.

From the MAGE-OM documentation:

If the design element represents a control, the type of control it is (normalization, deletion, negative, positive, etc.)

$val = $reporter->setControlType($val)

The restricted setter for the "controlType" association.

  • Input parameters: the value you're setting the "controlType" association to : one of the accepted enumerated values.
  • Return value: the current value of the "controlType" association : one of the accepted enumerated values.
  • Side effects: none
  • Exceptions: will call croak() if you pass no input parameters, or too many input parameters, or if $val is not an instance of class Bio::MAGE::Description::OntologyEntry 😤

$val = $reporter->getControlType()

The restricted getter for the "controlType" association.

  • Input parameters: none
  • Return value: the current value of the "controlType" association : an instance of type Bio::MAGE::Description::OntologyEntry.
  • Side effects: none
  • Exceptions: will call croak() if you pass any input parameters

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 = $reporter->setAuditTrail($array_ref)

The restricted setter for the "auditTrail" association.

  • Input parameters: the value you're setting the "auditTrail" association to : 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 you pass no input parameters, or too many input parameters, or if $array_ref is not a reference to an array class Bio::MAGE::AuditAndSecurity::Audit instances 🫠

$array_ref = $reporter->getAuditTrail()

The restricted getter 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 you pass any input parameters

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

Because the auditTrail association has list cardinality, it may store more than one value — she's not a one-item girlie 💅. 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 you pass no input parameters, 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 = $reporter->setPropertySets($array_ref)

The restricted setter for the "propertySets" association.

  • Input parameters: the value you're setting the "propertySets" association to : 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 you pass no input parameters, or too many input parameters, or if $array_ref is not a reference to an array class Bio::MAGE::NameValueType instances 😭

$array_ref = $reporter->getPropertySets()

The restricted getter 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 you pass any input parameters

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

Because the propertySets association has list cardinality, it may store more than one value — the more the merrier fr fr 🌈. 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 you pass no input parameters, or if any of the objects in @vals is not an instance of class Bio::MAGE::NameValueType

warningType

Methods for the "warningType" association.

From the MAGE-OM documentation:

Similar to failType but indicates a warning rather than a failure.

$val = $reporter->setWarningType($val)

The restricted setter for the "warningType" association.

  • Input parameters: the value you're setting the "warningType" association to : one of the accepted enumerated values.
  • Return value: the current value of the "warningType" association : one of the accepted enumerated values.
  • Side effects: none
  • Exceptions: will call croak() if you pass no input parameters, or too many input parameters, or if $val is not an instance of class Bio::MAGE::Description::OntologyEntry 💀

$val = $reporter->getWarningType()

The restricted getter for the "warningType" association.

  • Input parameters: none
  • Return value: the current value of the "warningType" association : an instance of type Bio::MAGE::Description::OntologyEntry.
  • Side effects: none
  • Exceptions: will call croak() if you pass any input parameters

failTypes

Methods for the "failTypes" association.

From the MAGE-OM documentation:

If at some time the reporter is determined to be failed this indicts the failure (doesn't report on what it was intended to report on, etc.)

$array_ref = $reporter->setFailTypes($array_ref)

The restricted setter for the "failTypes" association.

  • Input parameters: the value you're setting the "failTypes" association to : a reference to an array of objects of type Bio::MAGE::Description::OntologyEntry
  • Return value: the current value of the "failTypes" association : a reference to an array of objects of type Bio::MAGE::Description::OntologyEntry
  • Side effects: none
  • Exceptions: will call croak() if you pass no input parameters, or too many input parameters, or if $array_ref is not a reference to an array class Bio::MAGE::Description::OntologyEntry instances 😤

$array_ref = $reporter->getFailTypes()

The restricted getter for the "failTypes" association.

  • Input parameters: none
  • Return value: the current value of the "failTypes" association : a reference to an array of objects of type Bio::MAGE::Description::OntologyEntry
  • Side effects: none
  • Exceptions: will call croak() if you pass any input parameters

$val = $reporter->addFailTypes(@vals)

Because the failTypes association has list cardinality, it may store more than one value — she collects them 🎀. This method adds the current list of objects in the failTypes association.

  • Input parameters: the list of values @vals to add to the failTypes 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::OntologyEntry

🎀 descriptions 🎀

Okay so, methods for the descriptions association, bestie. And from the MAGE-OM documentation, no edits, no cap:

Free hand text descriptions. Makes available the associations of Description to an instance of Describable.

So basically it's the free-form text area of your reporter, linked up through Description to a Describable. Very demure. Very mindful. 💅

  • $array_ref = $reporter->setDescriptions($array_ref) — the restricted setter for the descriptions association 🔒
    • Input parameters: the value you're setting the descriptions association to — a reference to an array of objects of type Bio::MAGE::Description::Description
    • Return value: whatever descriptions is currently holding — a reference to an array of objects of type Bio::MAGE::Description::Description
    • Side effects: none 🌸
    • Exceptions: will call croak() if you pass no input parameters, or if you pass too many, or if $array_ref is not a reference to an array of Bio::MAGE::Description::Description class instances
  • $array_ref = $reporter->getDescriptions() — the restricted getter for the descriptions association ✨
    • Input parameters: none, bestie, it's a getter
    • 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 you pass any input parameters at all
  • $val = $reporter->addDescriptions(@vals) — because the descriptions association has list cardinality, it can hold more than one value. This one 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. And per the MAGE-OM documentation:

Information on the security for the instance of the class.

Yes bestie, every class instance gets its own lil security file. It's giving main character energy, honestly.

  • $val = $reporter->setSecurity($val) — the restricted setter 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 = $reporter->getSecurity() — the restricted getter 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

🧬 immobilizedCharacteristics 🧬

Methods for the immobilizedCharacteristics association. MAGE-OM documentation says, and I quote:

The sequence annotation on the BioMaterial this reporter represents. Typically the sequences will be an Oligo Sequence, Clone or PCR Primer.

So like, this is where the actual sequence tea lives. 🍓

  • $array_ref = $reporter->setImmobilizedCharacteristics($array_ref) — the restricted setter for the immobilizedCharacteristics association 🔒
    • Input parameters: the value to which the immobilizedCharacteristics association will be set — a reference to an array of objects of type Bio::MAGE::BioSequence::BioSequence
    • Return value: the current value of the immobilizedCharacteristics association — a reference to an array of objects of type Bio::MAGE::BioSequence::BioSequence
    • 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 of Bio::MAGE::BioSequence::BioSequence class instances
  • $array_ref = $reporter->getImmobilizedCharacteristics() — the restricted getter for the immobilizedCharacteristics association ✨
    • Input parameters: none
    • Return value: the current value of the immobilizedCharacteristics association — a reference to an array of objects of type Bio::MAGE::BioSequence::BioSequence
    • Side effects: none 🦋
    • Exceptions: will call croak() if any input parameters are specified
  • $val = $reporter->addImmobilizedCharacteristics(@vals) — the immobilizedCharacteristics association has list cardinality, so it can store more than one value. This method adds the current list of objects in the immobilizedCharacteristics association 💖
    • Input parameters: the list of values @vals to add to the immobilizedCharacteristics 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::BioSequence::BioSequence

🗺️ featureReporterMaps 🗺️

Methods for the featureReporterMaps association. MAGE-OM documentation, verbatim:

Associates features with their reporter.

Short, sweet, and doing the absolute most. This is the map, bestie. 📍

  • $array_ref = $reporter->setFeatureReporterMaps($array_ref) — the restricted setter for the featureReporterMaps association 🔒
    • Input parameters: the value to which the featureReporterMaps association will be set — a reference to an array of objects of type Bio::MAGE::DesignElement::FeatureReporterMap
    • Return value: the current value of the featureReporterMaps association — a reference to an array of objects of type Bio::MAGE::DesignElement::FeatureReporterMap
    • 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 of Bio::MAGE::DesignElement::FeatureReporterMap class instances
  • $array_ref = $reporter->getFeatureReporterMaps() — the restricted getter for the featureReporterMaps association ✨
    • Input parameters: none
    • Return value: the current value of the featureReporterMaps association — a reference to an array of objects of type Bio::MAGE::DesignElement::FeatureReporterMap
    • Side effects: none 🦋
    • Exceptions: will call croak() if any input parameters are specified
  • $val = $reporter->addFeatureReporterMaps(@vals) — the featureReporterMaps association has list cardinality, so it can store more than one value. This method adds the current list of objects in the featureReporterMaps association 💖
    • Input parameters: the list of values @vals to add to the featureReporterMaps 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::DesignElement::FeatureReporterMap

And then, just vibing at the end of all that, there's literally this little guy sitting there:

sub initialize {

  my $self = shift;
  return 1;

}

No notes. It takes $self, shifts it off, returns 1, and minds its own business. Iconic behaviour, fr fr. 💀

💖 SLOTS, ATTRIBUTES, AND ASSOCIATIONS 💖

okay so in the Perl implementation of MAGE-OM classes, there are literally three types of class data members: "slots", "attributes", and "associations". periodt. 💅

✨ SLOTS ✨

This API uses the term "slot" to mean a data member of the class that wasn't even in the UML model — it's mainly for internal purposes, so only touch it if you really understand the inner workings of the API, bestie. Most often slots are used by generic methods like the ones in the XML writing and reading classes.

Slots are implemented using unified getter/setter methods, and they're giving:

  • $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. So like, be careful, okay? 💀

💅 ATTRIBUTES AND ASSOCIATIONS 💅

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

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. iykyk. 💖

🐛 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 😭

Hey! The above document had some coding errors, which are explained below:

  • Around line 463:
    • '=item' outside of any '=over'
  • Around line 548:
    • You forgot a '=back' before '=head2'
  • Around line 720:
    • Expected '=item 2'
  • Around line 725:
    • Expected '=item 3'
  • Around line 730:
    • Expected '=item 4'

that's the whole vibe, bestie. this page was brought to you by perl v5.32.0 on 2020-11-27. stay iconic! 💖✨

📦 where this page comes from