Linux workstation

Upstream software project

libclass-accessor-perl

Automated accessor generation

About libclass-accessor-perl

Automated accessor generation

This project links 5 native package records across 5 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Debian 12 (Bookworm): 1 package records; Debian 13 (Trixie): 1 package records; Fedora 43: 1 package records; Fedora 44: 1 package records; openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.libclass-accessor-perl: recorded package coverageDebian 12 (Bookworm)1 recordsDebian 13 (Trixie)1 recordsFedora 431 recordsFedora 441 recordsopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
libclass-accessor-perl
Publisher
Not authoritatively mapped
Native package records
5
Operating systems
debian-12, debian-13, fedora-43, fedora-44, opensuse-tumbleweed
License expression
Artistic-1.0 OR GPL-1.0-or-later
Metadata completeness
100/100 (not a software quality rating)
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

This module automagically generates accessors/mutators for your class. Most of the time, writing accessors is an exercise in cutting and pasting. You usually wind up with a series of methods like this: sub name { my $self = shift; if(@_) { $self->{name} = $_[0]; } return $self->{name}; } sub salary { my $self = shift; if(@_) { $self->{salary} = $_[0]; } return $self->{salary}; } One for each piece of data in your object. While some will be unique, doing value checks and special storage tricks, most will simply be exercises in repetition. Not only is it Bad Style to have a bunch of repetitious code, but it's also simply not lazy, which is the real tragedy. If you make your module a subclass of Class::Accessor and declare your accessor fields with mk_accessors() then you'll find yourself with a set of automatically generated accessors which can even be customized! The basic set up is very simple: package Foo; use base qw(Class::Accessor); Foo->mk_accessors( qw(far bar car) ); Done. Foo now has simple far(), bar() and car() accessors defined. Alternatively, if you want to follow Damian's _best practice_ guidelines you can use: package Foo; use base qw(Class::Accessor); Foo->follow_best_practice; Foo->mk_accessors( qw(far bar car) ); *Note:* you must call 'follow_best_practice' before calling 'mk_accessors'.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 12 (Bookworm)

  1. libclass-accessor-perl

    Debian 12 (Bookworm) / perl

    0.51-2

    Perl module that automatically generates accessors

    allbookworm

Debian 13 (Trixie)

  1. libclass-accessor-perl

    Debian 13 (Trixie) / perl

    0.51-2

    Perl module that automatically generates accessors

    alltrixie

Fedora 43

  1. perl-Class-Accessor

    Fedora 43 / Unspecified / source perl-Class-Accessor

    0.51-23.fc43

    Automated accessor generation

    noarch43

Fedora 44

  1. perl-Class-Accessor

    Fedora 44 / Unspecified / source perl-Class-Accessor

    0.51-24.fc44

    Automated accessor generation

    noarch44

openSUSE Tumbleweed

  1. perl-Class-Accessor

    openSUSE Tumbleweed / Unspecified / source perl-Class-Accessor

    0.510.0-1.4

    Automated accessor generation

    noarchtumbleweed

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.