[erlang-questions] behaviour X undefined

[Torben Hoffmann]

On Fri, Jun 24, 2011 at 15:59, Joel Reymont <joelr1@REDACTED> wrote:

>
> On Jun 24, 2011, at 2:56 PM, Loïc Hoguin wrote:
>
> > I don't think an evil parameterized module can be used as a behaviour;
> > the behaviour_info/1 function will be undefined because you're
> > implicitly adding 3 parameters to it.
>
> Bummer! :-(
>
> It seems to work otherwise, though, in all aspects but the compilation
> warning.
>

I just tried to simulate what you were doing with a non-parameterised module
and it works like a charm, so this is probably the reason.

Cheers,
Torben


>
> --------------------------------------------------------------------------
> - for hire: mac osx device driver ninja, kernel extensions and usb drivers
> ---------------------+------------+---------------------------------------
> http://wagerlabs.com | @wagerlabs | http://www.linkedin.com/in/joelreymont
> ---------------------+------------+---------------------------------------
>
>
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>



-- 
http://www.linkedin.com/in/torbenhoffmann
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20110624/20b05e06/attachment.htm>