StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POIn Perl are there disadvantages to generating getters and setters rather than hard-coding them?
primarykey
Id
1390082
data
AcceptedAnswerId
1390525
AnswerCount
7
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2009-09-07T16:25:51.823
FavoriteCount
7
LastActivityDate
2017-04-21T15:32:38.880
LastEditDate
2009-09-07T16:58:23.987
LastEditorUserId
55857
OwnerUserId
55857
ParentId
0
PostTypeId
1
Score
7
ViewCount
1680
LastEditorDisplayName
text
Body
<p>In the example module below, the getters and setters are generated by adding anonymous subroutines to the symbol table. After the methods have been created in this manner, will the resulting code be functionally equivalent (in terms of behavior, speed, etc.) to a module with manually-written getters and setters, or does this approach have some sort of inherent liability? (I have done some basic speed benchmarking and have not detected any differences so far.)</p> <pre><code>package Module; use strict; use warnings; BEGIN { my @attr = qw(author title number); no strict 'refs'; for my $a (@attr){ *{__PACKAGE__ . "::get_$a"} = sub { $_[0]->{$a} }; *{__PACKAGE__ . "::set_$a"} = sub { $_[0]->{$a} = $_[1] }; } } sub new { my $class = shift; bless { @_ }, $class; } 1; </code></pre>
Tags
<perl><class><module><oop>
Title
In Perl are there disadvantages to generating getters and setters rather than hard-coding them?
singulars
PostAcceptedAnswerId
1. PO
  singulars
  PostTypePostTypeId
  PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USFMc
UserOwnerUserId
1. USFMc
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
  singulars
  PostTypePostTypeId
  PTAnswer
2. PO
  singulars
  PostTypePostTypeId
  PTAnswer
3. PO
  singulars
  PostTypePostTypeId
  PTAnswer
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  POIn Perl are there disadvantages to generating getters and setters rather than hard-coding them?
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
2. VO
  singulars
  PostPostId
  POIn Perl are there disadvantages to generating getters and setters rather than hard-coding them?
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
3. VO
  singulars
  PostPostId
  POIn Perl are there disadvantages to generating getters and setters rather than hard-coding them?
  UserUserId
  USsebthebert
  VoteTypeVoteTypeId
  VTFavorite
CommentsPostId
1. CO`*{"get_$a"} = sub` ... should also work. ( No need to have `__PACKAGE__` in there )
  singulars
  PostPostId
  POIn Perl are there disadvantages to generating getters and setters rather than hard-coding them?
  UserUserId
  USBrad Gilbert

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.