behaviours

[Fredrik Linder]

From: owner-erlang-questions@REDACTED
> [mailto:owner-erlang-questions@REDACTED]On Behalf Of Vlad Dumitrescu
>
> From: "Fredrik Linder" <fredrik.linder@REDACTED>
> > As an example I'd have:
> >
> >  o One behaviour to list operational functions (start/stop)
> >  o One behaviour to list administrative functions (set cache size/...)
> >  o One behaviour for each other functionality (add user/remove user or
> > permit_user/is_user_permitted or determine user violations (whatever))
> >
> > In this way I'd say that multiple behaviours are very desireable.
>
> This use of behaviours is more or less the same as interfaces are
> used in other
> languages.

True

> Just a thought that might open the can of snakes/worms/dragons :
> I think there
> is a difference in semantics for the two usages, maybe it would
> be appropriate
> to use different keywords? ...

I've thought about that too, but what is the real difference between
interfaces and behaviours? Is it really possible to differentiate the two?

Best
/Fredrik