Stories
Slash Boxes
Comments

NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

Why does Object::Tiny only support getters More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Immutable objects (Score:1)

by zby (4817)

Thanks for the reply, what you write here is very close to nothingmuch's two essays: Immutable Data Structures [woobling.org] and Immutable Data Structures (cont.) [woobling.org]. As a comp-sci graduate and ML programmer I like this style of programming and I understand very well these arguments, but just a few months ago, following links from Psychology of Perl talk links [einarsen.no], I encountered this article: Usability Implications of Requiring Parameters in Objects' Constructors [cmu.edu] which states:
A comparative study was performed to assess how pro
- Re: (Score:1)
  
  by hdp (1658)
  
  That article's irrelevant.
  1) We're talking about named constructor arguments vs. attribute setters, not positional constructor arguments vs. attribute setters; we already know that named > positional for readability, maintainability, etc. in most cases. OK, now we also know that that's even true if the named arguments are spread out over several lines of code. Big deal.
  2) How people interact with constructor arguments has absolutely nothing to do with the potential complexity of your objects introduced

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.