From: poptsov.artyom@gmail.com (Artyom V. Poptsov)
To: Guile Users' Mailing List <guile-user@gnu.org>
Subject: [ANN] Guile-INI 0.2.0
Date: Thu, 10 Jun 2021 21:29:40 +0300 [thread overview]
Message-ID: <87mtrxa7zf.fsf@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1906 bytes --]
Hello Guilers,
I'm pleased to announce Guile-INI 0.2.0 -- the first version of an INI
format[1] parser for GNU Guile:
https://github.com/artyom-poptsov/guile-ini/releases/tag/v0.2.0
Also Guile-INI is the first project that uses the Guile State Machine
Compiler (Guile-SMC)[2] to produce the finite state machine for the
parser from a PlantUML[3] state diagram, so you need Guile-SMC version
0.1.0 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.2.0 (2021-06-10)
** Update to use the new Guile-SMC 0.2.0 API
** Fix default =guilesitedir= and =ccachedir=
Guile-INI now uses correct values for these variables.
Thanks to Aleix Conchillo Flaqué
** Check for Guile-SMC
Guile-INI now checks for Guile-SMC when built.
Thanks to Aleix Conchillo Flaqué
** Validate the finite state machine
The FSM in PlantUML format now being validated during compilation.
** Changes in =ini->scm=
- Allow to read and store comments.
** Changes in =scm->ini=
- The procedure now accepts the "port" parameter as a keyword.
- Allow to write comments
** Changes in the =fsm.puml= file
- Bugfix: =trim_property_key= and =trim_property_value= states now do not
issue a syntax error when a letter is found.
- =read_section_title=: Issue syntax errors when an EOF object or a newline
found.
--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>
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 --]
next reply other threads:[~2021-06-10 18:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 18:29 Artyom V. Poptsov [this message]
2021-06-10 19:02 ` [ANN] Guile-INI 0.2.0 Zelphir Kaltstahl
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=87mtrxa7zf.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).