Re^2: Dynamic Method Generation Using Class::Accessor

Thanks for the input. I am trying to learn here, so could you elaborate on your comment about it not being a good idea to create the accessors. Would you recommend something like my $foo = $s->generic('foo'); Why is that beneficial (speed, maintainability?)? Thanks, David

Comment on Re^2: Dynamic Method Generation Using Class::Accessor Download Code

Replies are listed 'Best First'.
Re^3: Dynamic Method Generation Using Class::Accessor by moritz (Cardinal) on Aug 14, 2009 at 07:16 UTC
If you install methods for each new attribute, you install them in symbol table, which is shared among all objects. So whenever you install an accessor method for an object, all other objects get that too - although it doesn't make sense for them to have one. It also means that if you have a long running process, you might gather many methods which once were useful, but don't make sense anymore. Also consider the case where somebody might want to subclass your class, and can't know at the time of writing which methods your class will have - that's kinda painful.	[reply]

Replies are listed 'Best First'.

Re^3: Dynamic Method Generation Using Class::Accessor
by moritz (Cardinal) on Aug 14, 2009 at 07:16 UTC

So whenever you install an accessor method for an object, all other objects get that too - although it doesn't make sense for them to have one.

It also means that if you have a long running process, you might gather many methods which once were useful, but don't make sense anymore.

Also consider the case where somebody might want to subclass your class, and can't know at the time of writing which methods your class will have - that's kinda painful.

[reply]