-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EuroClojure 2017 Slide 14 Possible Error #21
Comments
I think some statements (like requiring core.match) are omitted on the slides for the sake of brevity. I'm checking the problem with exception now. |
Do you know of an Erlang example that is fairly complex, but not very complex, that I can "port" to otplike? I need to understand how to use otplike for my current project, and starting with a well understood Erlang example might be a good approach. Of course, I would contribute the port to the otplike project when I get it working. I'd probably need to ask you questions along the way. Is creating issues the way you would like me to ask questions? |
Yes, it would be very nice of you! It also makes it easier for others to find answers to the questions that have already been asked. |
The problem with the example is here: (gs/start-ns [])
Exception with the reason "noproc" means that caller is supposed to be a process. The problem can be fixed by wrapping the last (process/spawn
(process/proc-fn []
(let [[_ server] (gs/start-ns [])]
(println "2 + 3 = " (add server 2 3))))) We'll think about fixing this slide. |
I think of examples from the learnyousomeerlang book. Every chapter has one or more good examples supplementing explanation of a concept. I would started from examples given in this chapter. The book is also useful because it guides you step by step through the OTP principles. |
On slide 14 the following code is displayed:
In order to get it to compile from a "clean" "lein repl" I had to add the line
to the top of the code.
When I did, I received the following error:
I don't know what this means.
The text was updated successfully, but these errors were encountered: