Fri Jan 18 16:37:14 CET 2013
On 2013-01-18 16:32, Tony Rogvall wrote:
> Wow, this must be abused without hesitation.
Oh, good god.
Tony, when you put your brainpower into abusing Erlang code, Erlang
maintainers run scared. =)
> Really nice !
> On 18 jan 2013, at 16:25, Björn Gustavsson <bgustavsson@REDACTED
> <mailto:bgustavsson@REDACTED>> wrote:
>> On Tue, Jan 15, 2013 at 1:33 PM, Erik Reitsma <erlang@REDACTED
>> <mailto:erlang@REDACTED>> wrote:
>> On 01/15/2013 10:41 AM, Joe Armstrong wrote:
>>> Golly - I read the code - you modified error_handler.erl !!!!
>>> So what happens is ...
>>> I call android:fooBar(Args) - fooBar is not defined in
>>> so it's caught in error_handler and then android:rpc(fooBar,
>>> [...]) is called
>>> and this ends up as a Json call to a socket -
>> Yes, that is what happens.
>> It might interest you to know, that in R16, you can have a handler for
>> undefined functions in each module. (We needed that to implement the
>> transformation for parameterized modules.)
>> This new feature has just been merged to the master branch:
>> erlang-questions mailing list
>> erlang-questions@REDACTED <mailto:erlang-questions@REDACTED>
> "Installing applications can lead to corruption over time.
> Applications gradually write over each other's libraries, partial
> upgrades occur, user and system errors happen, and minute changes may
> be unnoticeable and difficult to fix"
> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions