<!DOCTYPE html><html><head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> </head> <body> Hi, Thanks! I was inspired by VPRI's ascii art language for tcp/ip stack. I thought it would be interesting if you could read directly (i.e. not trying to read N bytes to in-memory buffer then actually parse it) from network stream; that is, keep parsing and putting messages asynchronously into a shared queue, as they go. One thing that might be slightly worrying is additional indirection via BlockClosure evaluation, especially because it's valued in #everything method - the most fundamental rule for OMeta and might even further cripple performance for typical use cases. The idea was born out of distraction, so I didn't bother significantly rewriting fetching the next element but I think it's possible to avoid it - or just put the feature as preference? Cheaper to check "if" than always send #value. But hey, as was said some time ago: all problems in computer science can be solved by another level of indirection. Cheers, Michał <div class="moz-cite-prefix">On 17.07.2024 03:47, Phil B wrote: </div> <blockquote type="cite" cite="mid:CAMJMOejmmR6ACvGPJE-uABCJvHGFMpS4rOHG2JVS-2MLx_QLEw@mail.gmail.com"> <div dir="ltr">Very cool, I'll look at merging these as well. I've found OMeta quite useful over a network as well, though I tend to use higher level protocols (right now I mainly just piggyback on http/https using various 'web standards' to shuttle things back and forth which is handy when you only control the client or server, but not both) Things tend to get ugly when you start throwing network errors into the mix, but if you're in a clean networking environment where things are reliable/controlled, you could definitely have fun implementing (or even defining new) protocols in OMeta.</div> <div class="gmail_quote"> <div dir="ltr" class="gmail_attr">On Thu, Jun 20, 2024 at 10:18 AM Michał Olszewski via Cuis-dev <<a href="mailto:cuis-dev@lists.cuis.st" moz-do-not-send="true" class="moz-txt-link-freetext">cuis-dev@lists.cuis.st</a>> wrote: </div> <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi all, While working on a parser (uses text emphasis as part of the grammar btw.) for my bachelor's streaming language, I've strayed a bit and made a really small and fun experiment with OMeta2 serving as interpreter for simple message format being received from a SocketStream, showing versatility of OMeta in not just "local", finite pattern matching but also from push-pull streams, like network sockets. To enable it, I had to add small change to defer fetching next element from the stream. I attached necessary package and workspace contents. You can git clone OMeta with above fix from my repo: <a href="https://github.com/michalo1334/OMeta-Cuis" rel="noreferrer" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/michalo1334/OMeta-Cuis</a> Tested in Cuis7.0. Have fun! Cheers, Michał Possible TODO: implement parser/msg constructor for simple binary format like MessagePack and do message passing between objects across network. Implement everything in OMeta :). -- Cuis-dev mailing list <a href="mailto:Cuis-dev@lists.cuis.st" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">Cuis-dev@lists.cuis.st</a> <a href="https://lists.cuis.st/mailman/listinfo/cuis-dev" rel="noreferrer" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">https://lists.cuis.st/mailman/listinfo/cuis-dev</a> </blockquote> </div> </blockquote> </body> </html>