unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: poptsov.artyom@gmail.com (Artyom V. Poptsov)
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: guile-user@gnu.org
Subject: Re: [ANN] Guile-SMC 0.2.0
Date: Sun, 06 Jun 2021 22:47:34 +0300	[thread overview]
Message-ID: <87r1heai7d.fsf@gmail.com> (raw)
In-Reply-To: <87lf7m7q6e.fsf@web.de> (Arne Babenhauserheide's message of "Sun,  06 Jun 2021 21:23:37 +0200")

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

Hello!

Oh, I forgot to attach the NEWS part.  So here it goes, the "List of
User-Visible Changes":

--8<---------------cut here---------------start------------->8---
1 Version 0.2.0 (2021-06-06)
============================

1.1 Fix installation paths for source and compiled and files
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  - Compiled files are now installed to the right 'site-ccache' path.
  - Guile modules are now installed to the current Guile site directory
    by default.

  Thanks to Aleix Conchillo Flaqué.


1.2 Expand the Texinfo documentation
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


1.3 API changes
~~~~~~~~~~~~~~~

1.3.1 `(smc context context)': Bugfix
-------------------------------------

  The `<context>' would always have unexpected side effects due to field
  initialization with a single global instance of a <stack>. The
  instance would become shared between all the context in an
  application.

  Now the error is fixed.


1.3.2 `action:no-op' procedure moved to the context
---------------------------------------------------

  Now it's available from `(smc context char-context)' and `(smc context
      context)'.


1.3.3 All transition guards are now a part of Guile-SMC contexts
----------------------------------------------------------------

  There are modules in `(smc context)' name space that contain the
  transition guards.

  `(smc guards char)' is removed.


1.3.4 `(smc context char-context)': New module
----------------------------------------------

  This module contains a context for handling streams of characters.


1.3.5 In `(smc fsm)'
--------------------

* 1.3.5.1 New procedures in (smc fsm)

  - `fsm?'


* 1.3.5.2 Renames

  - `log-debug-transition' -> `fsm-log-transition'


1.4 Changes in `smc' program
~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1.4.1 Handle FSM validation independently
-----------------------------------------

  The `smc' tool now handles FSM validation (`--validation' flag)
  independently from e.g. compilation. Compilation stops when any
  problems in the output FSM are found.


1.4.2 Handle empty `modules' and `fsm-module' options
-----------------------------------------------------

  The program does not throw an error when the options left empty -- it
  uses default values instead.
--8<---------------cut here---------------end--------------->8---

- Artyom

-- 
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-06-06 19:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-06 18:58 [ANN] Guile-SMC 0.2.0 Artyom V. Poptsov
2021-06-06 19:23 ` Dr. Arne Babenhauserheide
2021-06-06 19:47   ` Artyom V. Poptsov [this message]
2021-06-06 21:52     ` Dr. Arne Babenhauserheide

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=87r1heai7d.fsf@gmail.com \
    --to=poptsov.artyom@gmail.com \
    --cc=arne_bab@web.de \
    --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).