I just noticed this the other day while playing around with erlydb and I was really confused when it worked. Glad that someone figured out what's going on. It seems like quite a coincidence that the first atom in the tuple was the module name which is what the Erlang idiom for OO would require. Then again, tagging the module/type at the beginning of the tuple feels like the right thing to do (it has to go somewhere, right?) and it makes a ton of sense that this idiom exists. Really cool.
I was sure that you had set up erlydb to work this way by design ;-). In the end it would lead to much cleaner code, so I'm all for reordering the parameters in the other functions. Dan PS Yariv, Let me know if you don't have time. I can tackle that and it would help me get up to speed on erlydb. On May 26, 7:34 pm, "Mikael Karlsson" <[EMAIL PROTECTED]> wrote: > 2008/5/26, Yariv Sadan <[EMAIL PROTECTED]>: > > > > > Hi, > > > I recently discovered in Erlang the capability to do OO-style method > > dispatch. It's pretty neat. I had no idea it worked but it does. > > ..... > > Hi, > > for those interested; there are som papers on this topic, called > parameterized modules: > Inheritance in erlang:http://www.erlang.se/euc/07/papers/1700Carlsson.pdf > Parameterized modules in > Erlang:http://www.erlang.se/workshop/2003/paper/p29-carlsson.pdf > > Mikael --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "erlyweb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en -~----------~----~----~----~------~----~------~--~---
