Please take our Survey
logo       

Choosing A Webhost:
A web hosting service is a type of Internet hosting service that allows individuals and organizations to provide their own website accessible via the World Wide Web. Web hosts are companies that provide space on a server they own for use by their clients as well as providing Internet connectivity, typically in a data center. Web hosts can also provide data center space and connectivity to the Internet for servers they do not own to be located in their data center, called colocation. more...

Re: Module Proposal: Package::Data::Inheritable: msg#00011

lang.perl.modules.authors

Subject: Re: Module Proposal: Package::Data::Inheritable

Bill Ward ha scritto:
On 9/4/07, Giacomo Cerrai <giantolo@xxxxxxxx> wrote:
A typical case I feel the need for that is when you have a hierarchy of
classes where you deal with a lot of data fields and you name them with
class data members:

our FIELDNAME1 = 'field1';
our FIELDNAME2 = 'field2';
...
our FIELDNAMEn = 'fieldn';

and then you use them like this:

foo({param1 => $val,
fields => { $FIELDNAME1 => $val1,
$FIELDNAME2 => $val2,
...
$FIELDNAMEn => $valn,
},
});
...
foreach my $field ($FIELD4, $FIELD2, ..., $FIELD10) {
...

With accessor methods this would be considerably more verbose:

foo({param => $val,
fields => { $SomeClass->FIELDNAME1 => $val1,
$SomeClass->FIELDNAME2 => $val2,
...
$SomeClass->FIELDNAMEn => $valn,
},
});
...
foreach my $field ($SomeClass->FIELD4, $SomeClass->FIELD2, ...,
$SomeClass->FIELD10) {
...

This becomes quickly unreadable and is not lazy.
Furthermore every fieldname access is a method call which is too much
overhead, especially when you have many fields to deal with.

If you put the field names into an array (or hash) then it becomes a lot easier.

our @FIELDNAMES = ( ... );
sub fieldnames { @FIELDNAMES };

my %fields;
my @names = $SomeClass->fieldnames();
@fields{@FIELDNAMES} = ($val1, $val2, ..., $valn);
foo({param1 => $val, fields => \%fields );
...
foreach my $field (@{$SomeClass->fieldnames()}) {
...

The set of fields a statement works on is not always the same.
Notice that the fields passed to foo() and the fields used in the
foreach are different.

cheers,
Giacomo





<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

Recently Viewed:
qnx.openqnx.dev...    gcc.libstdc++.c...    solaris.opensol...    information-ret...    misc.misterhous...    web.catalyst.ge...    apache.webservi...    redhat.release....    hardware.lirc/2...    kernel.autofs/2...    technology.sust...    linux.vdr/2003-...    editors.lyx.gen...    org.user-groups...    netbsd.devel.pk...    xdg.devel/2004-...    version-control...    jakarta.slide.d...    debian.packages...    creativecommons...    ports.ppc.embed...    bug-tracking.bu...   
Home | blog view | USPTO Patent Archive | advertise | OSDir is an inevitable website. super tiny logo

Free Magazines

Cisco News
Receive a free quarterly e-newsletter with exclusive articles on how Cisco IT uses its own products and solutions to enable the business.
subscribe

Systems Management News, the newspaper for IT systems administration and data center managers! Each issue of Systems Management News is chock-full of news and analysis to help you understand what's happening in your field.
subscribe

The Enterprise Newsweekly eWeek is the essential technology information source for builders of e-business.
subscribe

Oracle Magazine Oracle Magazine contains technology strategy articles, sample code, tips, Oracle and partner news, how to articles for developers and DBAs, and more. Oracle (NASDAQ: ORCL) is the world's largest enterprise software company.
subscribe

Total Telecom Total Telecom is "The Economist of the communications industry".
subscribe