unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: poptsov.artyom@gmail.com (Artyom V. Poptsov)
To: Guile Users' Mailing List <guile-user@gnu.org>
Subject: [ANN] Guile-SMC 0.1.0
Date: Sat, 01 May 2021 19:46:18 +0300	[thread overview]
Message-ID: <87h7jms8px.fsf@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1475 bytes --]

Hello,

I'm pleased to announce Guile State Machine Compiler (Guile-SMC), version
0.1.0:
  https://github.com/artyom-poptsov/guile-smc/releases/tag/v0.1.0

I'm hoping that it will ease the burden of writing format parsers and
other useful GNU Guile libraries for the community.


* What is Guile-SMC?

Guile-SMC is a state machine compiler that allows to describe finite
state machines (FSMs) in Scheme in terms of transition tables.  It is
capable to generate such transition tables from a PlantUML state
diagrams. [1]

A transition table can be verified and checked for dead-ends and
infinite loops.  Also Guile-SMC FSMs gather statistics when they run.

Guile-SMC comes with a Scheme program called 'smc' -- a state machine
compiler itself.  It produces a Scheme code for an FSM from the PlantUML
format.  This tool is meant to be called on a PlantUML file when a
program with a FSM is being built (for example, from a Makefile.)


* Usage examples

I wrote an INI[2] format parser to test the foundation ideas behind
Guile-SMC from the practical perspective:
  https://github.com/artyom-poptsov/guile-ini

I'm going to release it soon as well.


Happy hacking,

- Artyom

References:
1: https://plantuml.com/state-diagram
2: https://en.wikipedia.org/wiki/INI_file

-- 
Artyom "avp" Poptsov <poptsov.artyom@gmail.com>
CADR Hackerspace co-founder: https://cadrspace.ru/
GPG: D0C2 EAC1 3310 822D 98DE  B57C E9C5 A2D9 0898 A02F

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

                 reply	other threads:[~2021-05-01 16:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h7jms8px.fsf@gmail.com \
    --to=poptsov.artyom@gmail.com \
    --cc=guile-user@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).