<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">This is a great thread. I’m glad to see Xtreams Parsing getting better Actor examples. <div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Aug 12, 2019, at 9:11 PM, tim Rowledge <<a href="mailto:tim@rowledge.org" class="">tim@rowledge.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">What other value does Xtreams have?</span></div></blockquote></div><br class=""><div class="">It’s supposed to be an replacement for the Streams packages. All of it.</div><div class="">If I understand it correctly, Martin and Willow didn’t like the back and forth between read/write, so they made streams work like blocks. </div><div class="">It's a little beyond my pay grade so I’ll just give you the ESUG 2010 talk. [1]</div><div class=""><br class=""></div><div class="">Chris </div><div class=""><br class=""></div><div class="">[1] <a href="https://www.youtube.com/watch?v=fDGtPgDFMOU" class="">https://www.youtube.com/watch?v=fDGtPgDFMOU</a> </div><div class=""><br class=""></div></div></body></html>