8sync-0.3-released.skr 2.1 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253
  1. (post
  2. :title "8sync 0.3 released"
  3. :date (make-date* 2016 12 19 17 00)
  4. :tags '("release")
  5. :slug "8sync-0-3-released"
  6. (p [Greetings, all!
  7. I'm pleased to announce
  8. ,(anchor [8sync 0.3]
  9. "ftp://ftp.gnu.org/gnu/8sync/8sync-0.3.0.tar.gz")!
  10. 8sync is a library for
  11. ,(anchor [GNU Guile] "http://www.gnu.org/software/guile/")
  12. which provides an asynchronous event loop and which uses the
  13. actor model as its primary concurrency synchronization mechanism.])
  14. (p [This release brings some major changes and improvements.
  15. The
  16. ,(anchor [8sync 0.2]
  17. "https://www.gnu.org/software/8sync/news/8sync-02-released-and-the-future-of-8sync.html")
  18. release announcement (less than two weeks ago!) anticipated some of
  19. these changes.
  20. In summary:])
  21. (ul (li [8sync is now Guile 2.2 only, in order to support...])
  22. (li [Suspendable ports!
  23. Writing networked code is considerably simpler in 8sync 0.3.
  24. Using Guile 2.2's
  25. ,(anchor [suspendable ports]
  26. "https://www.gnu.org/software/guile/docs/master/guile.html/Non_002dBlocking-I_002fO.html")
  27. tooling, when reading and writing from ports that are set to
  28. be nonblocking, 8sync's scheduler will automatically
  29. suspend to the scheduler and resume your code when network
  30. data is ready to be handled.])
  31. (li [Actors now have an "actions" slot which is automatically
  32. inheritable.])
  33. (li ["define-mhandler" is deprecated.
  34. Instead, message handlers are simple procedures, and a
  35. message's body can be any sort of Guile procedure argument
  36. list.]))
  37. (p [And more!
  38. See the
  39. ,(anchor [NEWS file]
  40. "http://git.savannah.gnu.org/cgit/8sync.git/tree/NEWS?h=v0.3.0&id=29745029f85cbc462bcfa0c75f92156ea2c6b494")
  41. for full details.])
  42. (p [What's next?
  43. If all goes well, 8sync 0.4 should be around the corner soon as well.
  44. You can expect the actor system to be moved to take center stage
  45. in the application and (finally!) some decent documentation.])
  46. (p [Happy hacking!]))