Experimenting with bindings

I decided at the start that the hunt is open for all language features with Rye, but until above Rye 1.0, I won't be touching modules in any way. In Rebol they called it programming in the small vs. programming in the large. You want your language to function well in both.

If possible modules should come from the basic features of the language itself, so until those are in place it makes no sense to build on top of them. It's like making an elaborate plan on how to cross the river, when you have not seen the river yet. And the path to the river is as or even more challenging and important than the river crossing itself.

Currently, Rye has a very basic way of adding builtin functions / bindings / integrations to it. You compile them into a single binary. I think I saw something like that in Lua years ago.

This is not as bad as it seems. We use Go build's flags, so you can define, at compile time, what functionalities you want your Rye binary to have.

go build -flags "sqlite,httpd"

Example above builds a Rye interpreter with addition of sqlite and http server functionality. Compiling Rye with Go is quick and simple. There are no Makefiles or special scripts needed.

Still, this is much more cumbersome than for example Python's import statements. But it has some benefits too. Single binary is a simple, portable and non-conflicting concept. Python's default causes conflicts with conflicting versions of interpreters or python libraries. They had to invent virtualenv, venv, pyvenv and similar tools, to separate python environments. Our more primitive way enables us to simply do:

go build -flags "sqlite,httpd" -o ~/projects/A/ryel
go build -flags "psql,httpd2,crypto" -o ~/projects/B/ryel

rye .needs

We don't have modules, just compiled in bindings, but it's still beneficial to clearly declare the bindings that a script needs. And get alerted immediately when bindings aren't there, not fail at some later point of execution.

That's why I added a function, that returns a Rye interpreter object. And this object has some generic methods. Method needs lets you declare what binding script needs. includes? and can-include? are more useful for exploration, in Rye shell for example.

I also played with a more declarative way of producing local (per project) Rye interpreters. More about this in the future.

Follow Rye development on Github.

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