There's no /usr/include on Mojave.

* python/vcsn_cxx.cc: here.

* build-aux/m4/boost.m4: here.

It is no longer needed to declare how to hash a dynamic bit set.
Actually it is harmful.  This patch might need to be applied to
earlier versions of Boost, I don't know.

* vcsn/misc/dynamic_bitset.hh (hash<boost::dynamic_bitset<B, A>>):
Define only if Boost is older than 1.71.

* lib/vcsn/rat/parse.yy: here.

Bison 3.2 offers automove and move support for values.

* lib/vcsn/dot/parse.yy: Activate automove.
Adjust dependencies ($1 etc. are now rvalues, they can't be swapped
for instance).

Bison 3.2 allows to chose the name and place of the location.hh.  Use
this to share it from rat to vcsn/misc.

* lib/vcsn/rat/local.mk: Specify where to generate it.
* lib/vcsn/rat/parse.yy: Specify where to find it.

* python/vcsn_cxx.cc: here.

* Makefile.am (release.txt): New intermediate target.

Fix the build for recent versions of boost and bison

See merge request !6

Paul Hervot authored Aug 28, 2019 and Clément Démoulins committed Aug 28, 2019

Boost 1.69 introduced an ADL barrier on boost::distance(), so the call
that depended on it failed to build. Simply use qualified name lookup
instead.

See also https://github.com/boostorg/range/pull/75

.

* vcsn/core/rat/printer.hh: Fix.

Reported-by: Baptiste Esteban <baptiste.esteban@epita.fr>

Fix #214

That's only an initial stab.

* tests/tools/help.chk: s/$@/"$@"/.

No visible performance changes.

* tests/python/proper.dir/lan-poly.3.fail.gv,
* tests/python/proper.dir/lao-r.in.gv: These are actually daut files.

We parse in `lan, q`, we parse `<1/2>` as `<1/2>$`, not as `<1/2>\e`.
This is to support pre- and post-transition labels (e.g., `$ 0 <1/2>`).
Unfortunately it's easy, in particular with lao, to forget to write
`\e`, and I have been bitten: I tried to get the weight-series

    context = lao, expressionset<lal, q>
    $ -> 0
    0 -> 1 <a>
    1 -> 1 <b>
    1 -> 2 <c>
    2 -> $

But I got `<a+c>`.  The culprit was actually proper/is_proper: both
consider that automaton to be proper.  And the real culprit is
actually the user: there are indeed no spontaneous transitions in this
automaton: they are labeled with `$` because we did not use `\e`.
This error is too easy, so be sure to be kind to the user, and map the
special label to one when building the automaton.

It turns out that the test suite itself contained such an error: a
proper automaton still had a pseudo-spontaneous transition.

* vcsn/algos/edit-automaton.hh: Map $ to \e when adding an inner
transition.
* tests/python/proper.dir/lao-r.out.gv: Fix.

* vcsn/algos/edit-automaton.hh: there is not reason to accept
`$ 0 <1/2>\e`, spell it `$ 0 <1/2>`.

That "no" is useful for configure's logs, but not in our configuration
file.

A user has, in his config:

    ipython: no
    jupyter: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_vcsn/vcsn/work/vcsn-2.7/build-aux/bin/missing jupyter

This is not helpful in anyway.  In particular, `missing` is unlikely
to still be there when the user fires `vcsn jupyter`.

Leave a big fat nothing instead.

* tests/bin/ipynbdoctest.py: Let's try to look like the actual output
from IPython.  It's output is pretty-printed, but it does not look
like what I get using pprint.  They seem use the json module.

* tests/bin/update-test: Enable patches based on diffs.

It now fails when an exception escapes.

It took me way too long to understand the new failure...

To match the fact that dictionaries are sorted in Python 3.7, IPython
no longer sort the dictionaries when displaying
them (https://github.com/ipython/ipython/issues/10110).

So build them in the sorted order, so that our notebook tests produce
the expected output.

I wanted to know where OpenFST stands on is-deterministic when there
are spontaneous transitions.  The answer is: Open FST does not care
about them wrt determinism: the `one` label is treated like any other
label.

This is something I was considering for Vcsn too...  But I'm uneasy
with this, so I think I will rather introduce a new property P, and
define deterministic as having P and no spontaneous transitions.

See also #196.

* python/vcsn/automaton.py (fstinfo): New.
* tests/python/efsm.py: Check.

PATH etc. must be ready before being used.

I recently broke the install `vcsn`, as a result, (almost) nothing
works properly.  I didn't notice, because `make check` works, and we
run only it.

So try one installcheck for each arch, and speed/debug.