4 ms·
Can you explain why please?
by nathanwdavis 16y ago
Can you explain why please?
- gtani 16y agobackground on PD (tho i havent kept up with developments in R14, i can't say whether everything below still valid http://groups.google.com/group/erlang-programming/browse_frm/thread/15e3718c9fab68f7/c64371fee1f859f6?tvc=1#c64371fee1f859f6 http://groups.google.com/group/erlang-programming/browse_frm... ------------ (Oct 09) http://groups.google.com/group/erlang-programming/browse_frm/thread/8c5aac9e0ae91895/72683f33f1c4be85?tvc=1#72683f33f1c4be85 http://groups.google.com/group/erlang-programming/browse_frm...
- nathanwdavis 16y agoHey, great links. Thanks!!
- gtani 16y agoI think the consensus in 2009 was you should see how far you can get with ETS (and this will motivate me to read the R14 release notes), PD's are kind of like lisp reader macro's, very sharp and very slippery. There are many threads in the google group if you want more argumentage.
- gordonguthrie 16y agoIt has global state. In erlang processes are long lived and you bring functions to them to do stuff. Suddenly you will do something and a piece of state that you weren't expecting will be in your process dictionary... Some erlang processes run for literally years - and exist over multiple releases of the software. Reasoning about how something did or did not get into the process dictionary is for the birds.