behaviour again

[Per Bergqvist]

This might be the case for mnesia_access and megaco_encoder but
then what about mnesia_backup, mnesia_frag_hash and megaco_user ?

My non-educated guess is that mnesia_access and megaco_encoder 
doesn't even exist.

Shouldn't really the behaviours be defined or the behaviour 
reference be removed ?

/Per

-------------------
> 
> --- Per Bergqvist <per@REDACTED> wrote:
> > Hi,
> > 
> > the behaviours thread seemed to gain some interested
> > but did
> > not answer my question ...
> > 
> > Q: Why would one specify a behaviour without the
> > target
> > module implementing behaviour_info function ? (as in
> > mnesia and
> > megaco).
> 
> Like
> 
> -module(mnesia).
> -behaviour(mnesia_access).
> ...
> 
> My educated guess is that someone forgot to include
> mnesia_access.erl in the distribution :-)
> 
> Best,
> Thomas
> 
> 
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
> http://search.yahoo.com
> 
=========================================================
Per Bergqvist
Synapse Systems AB
Phone: +46 709 686 685
Email: per@REDACTED