Mobile code with isolated contexts

I read an interesting article. In it the writer is trying to send "code" for remote drawing over the websocket and execute it on the receiving end. He is doing it in JavaScript, but to demo the useful nature of lisp code structure (brackets).

He can't just send Javascript code and eval() it to do this, as you can't seem to really limit and control the the eval's context. So he makes a simple interpreter of a lisp like structures.

In Rye contexts/scopes are first class values. While making them I created a function isolate, that creates an totally isolated context. Let's try to use it to create something similar without the need to make a separate interpreter.

The receiver in the article draws graphical primitives to the screen, our will behave like some sort of old school printer.

First instruction

Fist the writer tried made calling one instruction possible. In his case it was drawLine, we will have a function print.

?word is a get-word. It returns the value behind the word but doesn't evaluate it.

Instruction composition

The writer then tried to compose two instructions (functions together). Since we evaluate normal rye language we can compose them as we would normally.

Let's add one user function to the printer.

Definitions

The writer then supported definitions, and custom function definition. Set-words already work inside our context, fn is just another function so we can add it.

Control structures

The article hints at also using if. All Rye control structures are just functions: if, either, loop ... So let's add loop for finish.

Final thoughts

Code sent through the wire here wouldn't be evaluated as a string, but loaded as all Rye code is into Rye values and those evaluated as all Rye code is.

Basically in one line we created our own little "language" with it's own little space (context).

Our isolated context can also be linked to other contexts and those to other. Since last blog-post Rye also has a concept of pure functions and an isolated context of just pure functions, so you could link your context to it and gain all the functionality without any side effects immediately.

Imagine that you have a server, or a worker and instead of translating desired functionality to individual REST calls you could just send it sequences of specific composable Rye code to execute and return the result.

Rye (as Rebol) give you the ability to create custom interpreters (dialects), but sometimes you don't even need that.

Komentarji

Priljubljene objave iz tega spletnega dnevnika

Less variables, more flows example vs Python

In the last blogpost ( Less variables, more flows ) I wrote a quick practical script I needed. It was an uncommon combination of CGI, two GET requests with Cookies and a POST request with Authorization header. I really like practical random/dirty problems, rather than ideal - made up problems to test the language. To get a sense of comparison I rewrote the example 2 times while removing specific Rye features. But that comparison is meaningless to a person that doesn't know Rye or at least Rebol already. So I went on fiverr and made a request for a Python script with these requirements. I got a nicely written Python script that uses functions for each step. To be more comparable, I rewrote the Rye code to a similar structure. Below is the result ... For a next step, it would be interesting, to extract a little simpler example out and add error handling. With Rye-s specific failure handling, I think the difference would become even greater. You can find Rye on github .

Preberite več

Ryelang - controlled file serving example and comparison to Python

This is as anecdotal as it gets, but basic HTTP serving functions in Rye seem to be working quite OK. They do directly use the extremely solid Go 's HTTP functions, so that should be somewhat expected. I made a ryelang.org web-server with few lines of Rye code 3 months ago and the process was running ever since and served more than 30.000 pages. If not else, it seems there are no inherent memory leaks in Rye interpreter. Those would probably show up in a 3 month long running process? And now I got another simple project. I needed to make a HTTP API for some mobile app. API should accept a key, and return / download a binary file in response if the key is correct. Otherwise it should return a HTTP error. So I strapped in and created Rye code below. I think I only needed to add generic methods stat and size? , all other were already implemented, which is a good sign. Of course, we are in an age of ChatGPT, so I used it to generate the equivalent Python code. It used the elegant

Preberite več

Receiving emails with Go's smtpd and Rye

This goes a while back. At some project for user support, we needed to receive emails and save them to appropriate databases. The best option back in the day seemed project Lamson . And it worked well ever since. It was written in Python by then quite known programmer Zed Shaw. It worked like a Python based SMTP server, that called your handlers when emails arrived. It was sort of Ruby on Rails for email. We were using this ever since. Now our system needs to be improved, there are still some emails or attachments that don't get parsed correctly. That isn't the problem of Lamson, but of our code that parses the emails. But Lamson development has been passive for more than 10 years. And I am already moving smaller utilities to Rye. Rye uses Go, and Go has this nice library smtpd , which seems like made for this task. I integrated it and parsemail into Rye and tested it in the Rye console first. Interesting function here is enter-console , that can put you into Rye console any

Preberite več

ryelang

Preišči ta spletni dnevnik