Preskoči na glavno vsebino

Rebol: making simple dialect using parse (dialect)

The Podcast

I was recently a guest on a developer oriented podcast Ogrodje. It's in Slovene language. It was great fun to meet two fellow developers and talk about tech and business. The second part of the podcast was about Rye. Because Rye is based on Rebol and because my projects are in big part made with Rebol, there was a lot of talk about Rebol too.

If you understand Slovene, you can listen to this and other episodes here: 

The Rebol

But it's hard to explain or even give a basic feeling about a language, if you can't show the code. Example tells a thousand words - to a programmer.

I tried to explain that Rebol is not just a little different Python, Ruby, JavaScript, but a small set of uniform ideas (that have more in common with scheme, forth, logo) and that "we" are still exploring how all we could use, to solve our problems (not my quote, can't find the original - it was cooler).

I found the one from Douglas Crockford, the inventor of JSON:

"a more modern language, but with some very similar ideas to Lisp, in that it's all built upon a representation of data which is then executable as programs"

The XML

I need to generate another set hairy XML-s for my work. The schema itself is named pain.008.002.01. When generating XML, I find the specification, the wide and many times unintuitive namespace the problematic part. 

It's not complex, it's just too wide, verbose and too temporal, to load it all into one's brain, understand, simplify and use. So implementing such XML usually consists of repeated empty looks into documentation and just plowing through it for hours or days, until it passes some XSD validation.

Back to Rebol

In most modern languages you solve problems by writing and composing the right functions, organized in classes/namespaces. In Rebol you can use those too, but if there is a big enough, repeated problem, you think to yourself:

"How would I ideally declare / describe the problem with Rebol values? And then you write an interpreter for that declaration."

In Rebol, we call these dialects. There are many dialects, the rebol "language" is just the "do" dialect, there is also the view (GUI) dialect, a draw dialect, a make dialect and the king of them all, the parse dialect, with which you can create your own dialects easily.

Parse is very capable, but  here are some basic examples that you can try to figure out:


 And back to XML

My idea was, to make XML definition less verbose and to have optional comments about what some node means directly next to them in the code. If I could declare the XML structure in this way, I would need less jumps to the documentation. Furthermore, I could generate an XML that includes all the comments, so XML is easier to check, understand and debug and without them.

Below is the code for the dialect and a small demo:

If the code seems odd, it's probably because Rebol conventions are still so foreign to you. When you get to know them, this code is quite simple. I wrote it ad-hoc in less than an hour today, and I haven't used parse seriously in years. 

OTOH if any Rebol guru is watching, you can propose improvements :).

(The text of this post is still improving)


Komentarji

Objavite komentar

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 .
Objavite komentar
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
Objavite komentar
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
Objavite komentar
Preberite več