(Non)Parametrized modules, inheritance, and R15B02 issues? - Erlang Programming

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion (Non)Parametrized modules, inheritance, and R15B02 issues?
Received-SPF: pass (google.com: domain of erlang-questions-boun...@erlang.org designates 192.121.151.104 as permitted sender) client-ip=192.121.151.104;
Mime-Version: 1.0 (Apple Message framework v1085)
From: Dmitry Belyaev <be.dmi...@gmail.com>
In-Reply-To: <FC0B0283-1F26-4291-97E6-E424E0FE8...@feuerlabs.com>
Date: Wed, 10 Oct 2012 13:18:08 +0400
Message-Id: <FEFF8404-D116-407D-B089-C7154922E...@gmail.com>
References: <865f8ce0-05c3-4b6e-b31d-b47724912841@zimbra>
 <FC0B0283-1F26-4291-97E6-E424E0FE8...@feuerlabs.com>
To: Ulf Wiger <u...@feuerlabs.com>
Cc: Tomas Morstein <t...@idea.cz>,
 "erlang-questi...@erlang.org" <erlang-questi...@erlang.org>
Subject: Re: [erlang-questions] (Non)Parametrized modules, inheritance,
	and R15B02 issues?
Precedence: list
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: erlang-questions-boun...@erlang.org
Sender: erlang-questions-boun...@erlang.org

My opinion is that parametrized modules are very nice for abstractions.

For example like these:
https://github.com/rabbitmq/erlando#monad-transformers

Of course it is doable without pmods. But it is doable with some kind of reinventing the wheel. Do we need to have non standard way to do the same thing?

-module(my_pmod).
-export([new/2, apply/2]).
-record(my_pmod, {module, thid}).

new(Module, Params) ->
	#my_pmod{module=Module, this=Params}.

apply(#my_pmod{module=Module, this=This}, Fun, Params) ->
	apply(Module, Fun, Params ++ [This]).

-- 
Dmitry Belyaev


On 10.10.2012, at 11:10, Ulf Wiger wrote:

> What would be good is if a list of good uses of pmods could
> be collected, and honorable workarounds suggested.
> 
> This could of course be done interactively on this list.
> Present what you think is code that is not easily done well
> without pmods, and let the members of this list debate
> suitable rewrites. If good alternatives are hard to find, 
> maybe that could inform some EEP for a more
> 'erlangish' extension that renders pmods truly obsolete?
> 
> BR,
> Ulf W
> 
> 
> On 10 okt 2012, at 00:54, Tomas Morstein <t...@idea.cz> wrote:
> 
>>>> ...
>> 
>> The problem starts when it comes to projects like ChicagoBoss
>> that we at IDEA love and intensively use every day.
>> CB uses pmods not only for simple_bridge-based web controllers,
>> but also for its sophisticated and well integrated concept of
>> data models being linked with Django templating engine in turn.
>> 
>> Although I fully understand reasons why pmods and their eventual
>> pseudo-OOP behaviour (like inheritance) are not so clear as they
>> are implemented today, but in other hand, many excellent projects
>> may disappear in final result...
>> 
>> I hope such a "total eclipse" is not going to happen, but our case
>> (over-using the extra unsupported and hackish features) we've just
>> adapted our technology to framework and totally forgot to standards,
>> what's in fact our own mistake.
> _______________________________________________
> erlang-questions mailing list
> erlang-questi...@erlang.org
> http://erlang.org/mailman/listinfo/erlang-questions

_______________________________________________
erlang-questions mailing list
erlang-questi...@erlang.org
http://erlang.org/mailman/listinfo/erlang-questions
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
