🖐 Vitas Comfama Bancolombia - Centro de Acondicionamiento Físico

putting it all togather, it's very verbose to handle errors in erlang. use try expression's of section to pattern match the error value. for exceptions of class throw, that is the code called throw term , term is returned. we have to use the patter match for the conditional execution. you can use try expression or catch expression try expression is strightforward, if you ignore the awkward erlang grammer that is. walkthrough of hello world http server with erlang, cowboy, and rebar3 instead of returning the hello world, we're going to return the sum of two query parameter a, b. well, at least, i understand the error handling of erlang.{/INSERTKEYS}{/PARAGRAPH} the simplest code that assume no error will be like this. suppose, the users forget the query parameters. we can do condional branching with either case expression or function pattern match. the erlang has three class of exception: error, exit, and throw. it's too verbose and ugly but i think alternatives are worse. if you don't care about exception, you need to do nothing. here is the verbose code. the catch expression. {PARAGRAPH}{INSERTKEYS}so hopefully, the higher framework catch these exceptions and restart the process. but if you care, that is, you want to run some code on the condition of exception, things get verbose. but i want to deal the the error. erlang has exception like many other langauges. but what if the caller want to deal with the error? catch exprs catch expression evaluate exprs and return its value on no exception. another type of error is although the query paramters are present, it has a string that cannot be parsed as an integer. well, it's not bad. try expression can have of section and it will be evaluated only on no exception in exprs. it can be done by case expression or function. let's quickly borrow a code from the hello world http server i explained in the previous article. but i feel some oddities on erlang's exception and that is the concept of class. after consdering the various code, i come up with this code. my guess is to keep the backward compatibility. whichever you use, it became quite verbose and boilar-plate.