I think the point is that if you use @ and then later redesign the internals of the class so that that component is not longer stored but is, instead, computed then @ will no longer be possible to use in that instance and a method call will be required which means that the internal change implies that the user interface must change. Of course, that is undesirable. In some programming languages like Python one can access a variable and call a function using the exact same syntax so that it would be possible to make such an internal change without affecting the user.
On 9/26/06, Sebastian P. Luque <[EMAIL PROTECTED]> wrote: > Hi, > > I'm usually confused about when to use 'slot' or '@'. I've frequently > read that it's always preferable to use accessor functions, so I would > think the '@' operator should be avoided. However, ?slot contains the > following advise: > > > "Generally, the only reason to use the functional form rather than the > simpler operator is _because_ the slot name has to be computed." > > > How do we decide whether to use the function or the operator? > > > Cheers, > > -- > Seb > > ______________________________________________ > R-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel > ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
