Re^2: The Accessor Heresy

Using a cascaded if/elsif/else instead of individual methods looks terribly awkward to me. I think that's part of what OO and methods (or even subroutines in general) are supposed to help us avoid!

Comment on Re^2: The Accessor Heresy

Replies are listed 'Best First'.
Re^3: The Accessor Heresy by radiantmatrix (Parson) on Nov 29, 2005 at 16:03 UTC
Yes, the implementation is poor, but it is meant to be a simple demonstration. I tend to choose dispatch-table type patterns for such things, and if the normalization/etc. were more complex I might even have "private" subroutines to deal with the attributes. My post is more targetted toward interface than internal implementation; still, your point is a good one. <-radiant.matrix-> A collection of thoughts and links from the minds of geeks The Code that can be seen is not the true Code "In any sufficiently large group of people, most are idiots" - Kaa's Law	[reply]

Replies are listed 'Best First'.

Re^3: The Accessor Heresy
by radiantmatrix (Parson) on Nov 29, 2005 at 16:03 UTC

Yes, the implementation is poor, but it is meant to be a simple demonstration. I tend to choose dispatch-table type patterns for such things, and if the normalization/etc. were more complex I might even have "private" subroutines to deal with the attributes.

My post is more targetted toward interface than internal implementation; still, your point is a good one.

<-radiant.matrix->
A collection of thoughts and links from the minds of geeks
The Code that can be seen is not the true Code
"In any sufficiently large group of people, most are idiots" - Kaa's Law

[reply]