Rye meets Raylib #2 (more namespacing)

This is a continuation from the previous post.

When we communicate, which programming is, we try to be not overly verbose and redundant. Communication between people usually happens inside some context hierarchy. A fork when two programmers chat is a different thing than when two chefs do.

One of the goals of Rye is to enable succinct, well flowing code and use of short words for functions helps with that. That's why generic methods are an important part of the language. Many times the first argument providing the context works well. But sometimes this is redundant also.

Given that the contexts/scopes are first class Rye values, we can construct a context that holds all words of our Raylib game engine. Contexts can link to parent context, so Raylib words have a priority, but everything else works as normal.

Let's create this context:

And use it. Comparable Go code is on the left:

Because we can create custom "looping constructs" in Rye, I just replaced for loop and a condition check with a simpler world main-loop that does this.

We already had a function do-in (context), but with-context sounded clearer here so I renamed it. There are also other ways to run code with a given context, for examples via word fnc on a function level.

A little more involved example below makes the golden ball continuously travel from the left to the right of the window.

Btw. I started writing Rye at a glance on the readme page on github repo.

Komentarji

Priljubljene objave iz tega spletnega dnevnika

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 ele...

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č

Go's concurrency in a dynamic language Rye

The Rye programming language is a dynamic scripting language based on REBOL’s ideas, taking inspiration from the Factor language and Unix shell. Rye is written in Go and inherits Go’s concurrency capabilities, including goroutines and channels. Recently, Rye gained support for Go’s select and waitgroups. Building blocks Goroutines Goroutines are lightweight threads of execution that are managed by the Go/Rye runtime. They operate independently, allowing multiple tasks to run concurrently without blocking each other. Creating a Goroutine in Rye is straightforward. The go keyword is used to launch a new Goroutine, followed by the Rye function to be executed concurrently. For instance, the following code snippet creates and starts a Goroutine that prints a message after a delay: ; # Hello Goroutine print "Starting Goroutine" go does { ; does creates a function without arguments sleep 1000 print "Hello from Goroutine!" } print "Sleepi...

Preberite več

ryelang

Preišči ta spletni dnevnik