caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Jocelyn Sérot" <Jocelyn.Serot@univ-bpclermont.fr>
To: caml users <caml-list@inria.fr>
Subject: [Caml-list] [ANN] LASCAr - A library for manipulating Labeled Transition Systems
Date: Tue, 7 Nov 2017 18:40:25 +0100	[thread overview]
Message-ID: <9664A23D-010B-40E4-A8BC-5AE273EE50D6@univ-bpclermont.fr> (raw)

I'm pleased to announce the first release of LASCAr, an OCaml library for manipulating Labeled Transition Systems.

The library provides, in particular, functions for
- building and inspecting models of such systems
- generating graphical (`.dot` format) and text (`.tex` format) representations
- computing execution trees and displaying them in graphical or text format
- computing the product (in various flavors) of such systems

Its provides implementations both for "generic" LTS (with or without state attributes) and for "specialized" versions such as
- deterministic and non-deterministic finite automata (DFA, NFA),
- Mealy and Moore automata
- Finite State Machines (FSMs)

The source code, documentation and some examples can be downloaded from GitHub at : 

https://github.com/jserot/lascar

For a quick glance, some annotated code snippets are available here

http://htmlpreview.github.io/?https://github.com/jserot/lascar/blob/master/doc/examples/examples.html

The API is documented here 

http://htmlpreview.github.io/?https://github.com/jserot/lascar/blob/master/doc/api/lascar.html

Contributions are welcome since this kind of library is, due to pervasive nature of LTS, highly extensible in many ways.
[please note that, since i’m new to GitHub, any advice on how to handle this would be appreciated].

J. Sérot

                 reply	other threads:[~2017-11-07 17:40 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

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

  git send-email \
    --in-reply-to=9664A23D-010B-40E4-A8BC-5AE273EE50D6@univ-bpclermont.fr \
    --to=jocelyn.serot@univ-bpclermont.fr \
    --cc=caml-list@inria.fr \
    /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 NNTP newsgroup(s).