Private attribute or accessor?

S

Sam Kong

Hi!

See the following codes.

[1]
class C
attr_accessor :a
def f(v)
@a = v
...
end
end

[2]
class C
attr_accessor :a
def f(v)
a = v
...
end
end


[1] and [2] work exactly same.
I wonder which way is more proper.

In my opinion, if there're accessors (getter and setter), using them in
the class is better than directly accessing the instance data.
However, most codes I've seen access the data directly.

What do you think?

Sam
 
J

Joel VanderWerf

Sam said:
In my opinion, if there're accessors (getter and setter), using them in
the class is better than directly accessing the instance data.
However, most codes I've seen access the data directly.

What do you think?

I tend to agree. It's more flexible if you later need to redefine the
accessors to do some extra computation or store the value differently.
 
M

Matthew Desmarais

Sam said:
Hi!

See the following codes.

[1]
class C
attr_accessor :a
def f(v)
@a = v
...
end
end

[2]
class C
attr_accessor :a
def f(v)
a = v
...
end
end


[1] and [2] work exactly same.
I wonder which way is more proper.

In my opinion, if there're accessors (getter and setter), using them in
the class is better than directly accessing the instance data.
However, most codes I've seen access the data directly.

What do you think?

Sam
Hi Sam,

Just a quick point: your examples don't work the same way. In [2],
you'll want to replace a = v with self.a = v.

Regards,
Matthew
 
A

Alex Fenton

Sam said:
In my opinion, if there're accessors (getter and setter), using them in
the class is better than directly accessing the instance data.
However, most codes I've seen access the data directly.

Another advantage of using accessor methods (self.foo = ) over variables (@foo =) is that it can help avoid typo bugs. Variables are initialised to nil, so if you write @the_variable in one place and later elsewhere read @thevariable, you don't get an immediate complaint. If you typo an accessor method, you get an immediate NoMethodError .

I've moved to this style over time - also because it's easier (I find) to do things using method reflection - eg adding and notifying observers.

a
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
474,201
Messages
2,571,048
Members
47,646
Latest member
xayaci5906

Latest Threads

Top