unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Artyom V. Poptsov" <poptsov.artyom@gmail.com>
To: Guile Users' Mailing List <guile-user@gnu.org>
Subject: [ANN] Guile-INI 0.5.2 released
Date: Sun, 25 Sep 2022 06:12:47 +0300	[thread overview]
Message-ID: <8735cgno40.fsf@gmail.com> (raw)

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

Hello Guilers,

I'm pleased to announce Guile-INI 0.5.2, an INI format[1] parser for GNU
Guile:
  https://github.com/artyom-poptsov/guile-ini/releases/tag/v0.5.2

Note that Guile-INI uses the Guile State Machine Compiler (Guile-SMC)[2]
to produce the finite state machine for the parser from a PlantUML[3]
state diagram, and you need Guile-SMC version 0.5.2 to compile Guile-INI.


* The list of user-visible changes

Here's an excerpt from the NEWS file:

--8<---------------cut here---------------start------------->8---
* Version 0.5.2 (2022-09-24)
** =ini->scm=: Fix the debug mode
Load =fsm-statistics= procedure from =(smc fsm)= module when debug mode is
enabled.
** Fix build order
Now Guile-SMC intermediate context is generated before the files that depend
on it.

Reported by Aleix Conchillo Flaqué here:
<https://github.com/artyom-poptsov/guile-ini/pull/3>
** Fix =make distcheck=
Guile-INI now successfully builds with =make distcheck=.
--8<---------------cut here---------------end--------------->8---


Thanks,

- Artyom


References:
1. http://www.catb.org/~esr/writings/taoup/html/ch05s02.html#id2907263
2. https://github.com/artyom-poptsov/guile-smc
3. https://plantuml.com/state-diagram

-- 
Artyom "avp" Poptsov <poptsov.artyom@gmail.com>
Home page: https://memory-heap.org/~avp/
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: 519 bytes --]

                 reply	other threads:[~2022-09-25  3:12 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=8735cgno40.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).