[erlang-questions] Why doesn't Erlang has return statement?
Wed Dec 17 03:51:50 CET 2014
I recommend giving Garrett's video below a watch to overcome your fear of
adding more functions. I've always been skeptical of the approach, but I
forced myself to try it and it actually works out really well.
On Tue, Dec 16, 2014 at 2:05 AM, aman mangal <mangalaman93@REDACTED> 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
> Thank you
> Aman Mangal
> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions