Since Interface is already the name of a Ruby library, pretty much any
other word (as long as it doesn't similarly shadow an existing
package) is automatically more suitable than Interface.
"Interfaces" and "Interfacer" come to mind -- not plum names, perhaps,
but (as far as I know) unambiguous and unclaimed in Ruby-space.
David
i'm with david.
from an objective-c website:
"Protocols:
Protocols, like the name hints, are definitions of behavior which a group of
classes can conform to. Protocols have no interface or implementation, but
they more resemble an interface. You don't add new instance variables, nor do
you add new methods or define the internal workings of any method. All a
protocol does is to define a set of methods which a class must contain in
order to conform to this the protocol. "
i kind of like it better than 'interface', which sounds too java-ish for my
tastes....
-a
--
===============================================================================
| EMAIL :: Ara [dot] T [dot] Howard [at] noaa [dot] gov
| PHONE :: 303.497.6469
| A flower falls, even though we love it; and a weed grows, even though we do
| not love it. --Dogen
===============================================================================