[erlang-questions] blunt error reporting by escript

Ulf Wiger <>
Wed Sep 10 14:21:07 CEST 2008


Yes, I do that already.

/Ulf

2008/9/10 Bengt Kleberg <>:
> Greetings,
>
> While waiting for escript to get better error reporting have you
> considered using:
>
> a() ->
> {_, {ok, Value}} = {a, call_that_should_return_ok_value()}.
>
> b() ->
> {_, {ok, Value}} = {b, call_that_should_return_ok_value()}.
>
> bengt
>
> On Tue, 2008-09-09 at 16:58 +0200, Ulf Wiger wrote:
>> I'm writing a non-trivial escript script, and am getting pretty
>> frustrated with the error reporting.
>>
>> escript: exception error: no match of right hand side value {ok, ["..."]}
>>
>> My script is only 75 lines so far but has 10 different functions, and it would
>> certainly help to at least know in which function the error occured,
>> if not the line.
>>
>> If the script is interpreted, couldn't it give me the line number?
>> I'd even forego the pretty-printing of the message in favor of some hard
>> facts about where in the program the exception happened.
>>
>> BR,
>> Ulf W
>> _______________________________________________
>> erlang-questions mailing list
>> 
>> http://www.erlang.org/mailman/listinfo/erlang-questions
>
> _______________________________________________
> erlang-questions mailing list
> 
> http://www.erlang.org/mailman/listinfo/erlang-questions
>



More information about the erlang-questions mailing list