[erlang-questions] Why doesn't Erlang has return statement?

Dmitry Belyaev <>
Wed Dec 17 08:59:52 CET 2014


Although erlang doesn't have return statement, it's not very hard to implement a substitute.

Here is a toy I made but never used: https://github.com/RumataEstor/ereturn

-- 
Best wishes,
Dmitry Belyaev

On 16 December 2014 7:05:08 PM AEDT, aman mangal <> wrote:
>Hi everyone,
>
>I have seen similar questions before on the forum but I could never
>understand the reason behind it. Is it due to theoretical reasons such
>as *return
>*statement makes it hard to reason about the program or practical
>reasons
>that it is hard to implement it (this doesn't seem right but I cannot
>think
>of anything else)?
>
>Moreover, is there a good alternate to avoid nested case statements?
>Making
>more functions just seems tedious. Using *catch *statement seems
>another
>good alternate but my intuition is that it is not good practice, is it?
>
>Thank you
>Aman Mangal
>www.prism.gatech.edu/~amangal7
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>erlang-questions mailing list
>
>http://erlang.org/mailman/listinfo/erlang-questions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20141217/a4f79e52/attachment.html>


More information about the erlang-questions mailing list