[erlang-questions] Erlang4Android

Björn-Egil Dahlberg egil@REDACTED
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. =)

// Björn-Egil

> Really nice !
>
> /Tony
>
> 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
>>>     android.erl
>>>        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 
>> parse
>> transformation for parameterized modules.)
>>
>> This new feature has just been merged to the master branch:
>>
>> https://github.com/erlang/otp/commit/209a479080214ab901116d48b90e91d6c056278d
>>
>> /Bjorn
>>
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED <mailto:erlang-questions@REDACTED>
>> http://erlang.org/mailman/listinfo/erlang-questions
>
> "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
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20130118/a8deff9d/attachment.htm>


More information about the erlang-questions mailing list