summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/xint/CHANGES.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/generic/xint/CHANGES.html')
-rw-r--r--Master/texmf-dist/doc/generic/xint/CHANGES.html234
1 files changed, 147 insertions, 87 deletions
diff --git a/Master/texmf-dist/doc/generic/xint/CHANGES.html b/Master/texmf-dist/doc/generic/xint/CHANGES.html
index 7055bf2e04e..c55d211a14e 100644
--- a/Master/texmf-dist/doc/generic/xint/CHANGES.html
+++ b/Master/texmf-dist/doc/generic/xint/CHANGES.html
@@ -4,7 +4,7 @@
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
- <meta name="author" content="xint 1.4k" />
+ <meta name="author" content="xint 1.4l" />
<title>CHANGE LOG</title>
<style>
html {
@@ -170,35 +170,44 @@
<body>
<header id="title-block-header">
<h1 class="title">CHANGE LOG</h1>
-<p class="author">xint 1.4k</p>
-<p class="date">2022/05/18</p>
+<p class="author">xint 1.4l</p>
+<p class="date">2022/05/29</p>
</header>
<nav id="TOC" role="doc-toc">
<ul>
+<li><a href="#l-20220529"
+id="toc-l-20220529"><code>1.4l (2022/05/29)</code></a>
+<ul>
+<li><a href="#bug-fixes" id="toc-bug-fixes">Bug fixes</a></li>
+<li><a href="#new-features" id="toc-new-features">New features</a></li>
+<li><a href="#documentation"
+id="toc-documentation">Documentation</a></li>
+</ul></li>
<li><a href="#k-20220518"
id="toc-k-20220518"><code>1.4k (2022/05/18)</code></a>
<ul>
<li><a href="#breaking-changes" id="toc-breaking-changes">Breaking
changes</a></li>
-<li><a href="#bug-fixes" id="toc-bug-fixes">Bug fixes</a></li>
-<li><a href="#new-features" id="toc-new-features">New features</a></li>
+<li><a href="#bug-fixes-1" id="toc-bug-fixes-1">Bug fixes</a></li>
+<li><a href="#new-features-1" id="toc-new-features-1">New
+features</a></li>
</ul></li>
<li><a href="#j-20210713"
id="toc-j-20210713"><code>1.4j (2021/07/13)</code></a>
<ul>
-<li><a href="#bug-fixes-1" id="toc-bug-fixes-1">Bug fixes</a></li>
+<li><a href="#bug-fixes-2" id="toc-bug-fixes-2">Bug fixes</a></li>
</ul></li>
<li><a href="#i-20210611"
id="toc-i-20210611"><code>1.4i (2021/06/11)</code></a>
<ul>
-<li><a href="#new-features-1" id="toc-new-features-1">New
+<li><a href="#new-features-2" id="toc-new-features-2">New
features</a></li>
-<li><a href="#bug-fixes-2" id="toc-bug-fixes-2">Bug fixes</a></li>
+<li><a href="#bug-fixes-3" id="toc-bug-fixes-3">Bug fixes</a></li>
</ul></li>
<li><a href="#h-20210527"
id="toc-h-20210527"><code>1.4h (2021/05/27)</code></a>
<ul>
-<li><a href="#bug-fixes-3" id="toc-bug-fixes-3">Bug fixes</a></li>
+<li><a href="#bug-fixes-4" id="toc-bug-fixes-4">Bug fixes</a></li>
</ul></li>
<li><a href="#g-20210525"
id="toc-g-20210525"><code>1.4g (2021/05/25)</code></a>
@@ -206,54 +215,54 @@ id="toc-g-20210525"><code>1.4g (2021/05/25)</code></a>
<li><a href="#breaking-changes-1" id="toc-breaking-changes-1">Breaking
changes</a></li>
<li><a href="#deprecated" id="toc-deprecated">Deprecated</a></li>
-<li><a href="#new-features-2" id="toc-new-features-2">New
+<li><a href="#new-features-3" id="toc-new-features-3">New
features</a></li>
-<li><a href="#bug-fixes-4" id="toc-bug-fixes-4">Bug fixes</a></li>
+<li><a href="#bug-fixes-5" id="toc-bug-fixes-5">Bug fixes</a></li>
</ul></li>
<li><a href="#f-20210510"
id="toc-f-20210510"><code>1.4f (2021/05/10)</code></a>
<ul>
<li><a href="#breaking-changes-2" id="toc-breaking-changes-2">Breaking
changes</a></li>
-<li><a href="#bug-fixes-5" id="toc-bug-fixes-5">Bug fixes</a></li>
+<li><a href="#bug-fixes-6" id="toc-bug-fixes-6">Bug fixes</a></li>
</ul></li>
<li><a href="#e-20210505"
id="toc-e-20210505"><code>1.4e (2021/05/05)</code></a>
<ul>
<li><a href="#breaking-changes-3" id="toc-breaking-changes-3">Breaking
changes</a></li>
-<li><a href="#new-features-3" id="toc-new-features-3">New
+<li><a href="#new-features-4" id="toc-new-features-4">New
features</a></li>
-<li><a href="#bug-fixes-6" id="toc-bug-fixes-6">Bug fixes</a></li>
+<li><a href="#bug-fixes-7" id="toc-bug-fixes-7">Bug fixes</a></li>
</ul></li>
<li><a href="#d-20210329"
id="toc-d-20210329"><code>1.4d (2021/03/29)</code></a>
<ul>
<li><a href="#breaking-changes-4" id="toc-breaking-changes-4">Breaking
changes</a></li>
-<li><a href="#bug-fixes-7" id="toc-bug-fixes-7">Bug fixes</a></li>
+<li><a href="#bug-fixes-8" id="toc-bug-fixes-8">Bug fixes</a></li>
</ul></li>
<li><a href="#c-20210220"
id="toc-c-20210220"><code>1.4c (2021/02/20)</code></a>
<ul>
-<li><a href="#bug-fixes-8" id="toc-bug-fixes-8">Bug fixes</a></li>
+<li><a href="#bug-fixes-9" id="toc-bug-fixes-9">Bug fixes</a></li>
</ul></li>
<li><a href="#b-20200225"
id="toc-b-20200225"><code>1.4b (2020/02/25)</code></a>
<ul>
<li><a href="#future" id="toc-future">Future</a></li>
-<li><a href="#new-features-4" id="toc-new-features-4">New
+<li><a href="#new-features-5" id="toc-new-features-5">New
features</a></li>
-<li><a href="#bug-fixes-9" id="toc-bug-fixes-9">Bug fixes</a></li>
+<li><a href="#bug-fixes-10" id="toc-bug-fixes-10">Bug fixes</a></li>
</ul></li>
<li><a href="#a-20200219"
id="toc-a-20200219"><code>1.4a (2020/02/19)</code></a>
<ul>
<li><a href="#breaking-changes-5" id="toc-breaking-changes-5">Breaking
changes</a></li>
-<li><a href="#new-features-5" id="toc-new-features-5">New
+<li><a href="#new-features-6" id="toc-new-features-6">New
features</a></li>
-<li><a href="#bug-fixes-10" id="toc-bug-fixes-10">Bug fixes</a></li>
+<li><a href="#bug-fixes-11" id="toc-bug-fixes-11">Bug fixes</a></li>
</ul></li>
<li><a href="#section"
id="toc-section"><code>1.4 (2020/01/31)</code></a>
@@ -263,7 +272,7 @@ changes</a></li>
<li><a href="#improvements-and-new-features"
id="toc-improvements-and-new-features">Improvements and new
features</a></li>
-<li><a href="#bug-fixes-11" id="toc-bug-fixes-11">Bug fixes</a></li>
+<li><a href="#bug-fixes-12" id="toc-bug-fixes-12">Bug fixes</a></li>
<li><a href="#todo" id="toc-todo">TODO</a></li>
</ul></li>
<li><a href="#f-20190910"
@@ -272,7 +281,7 @@ id="toc-f-20190910"><code>1.3f (2019/09/10)</code></a>
<li><a href="#improvements-and-new-features-1"
id="toc-improvements-and-new-features-1">Improvements and new
features</a></li>
-<li><a href="#bug-fixes-12" id="toc-bug-fixes-12">Bug fixes</a></li>
+<li><a href="#bug-fixes-13" id="toc-bug-fixes-13">Bug fixes</a></li>
</ul></li>
<li><a href="#e-20190405"
id="toc-e-20190405"><code>1.3e (2019/04/05)</code></a>
@@ -282,7 +291,7 @@ changes</a></li>
<li><a href="#improvements-and-new-features-2"
id="toc-improvements-and-new-features-2">Improvements and new
features</a></li>
-<li><a href="#bug-fixes-13" id="toc-bug-fixes-13">Bug fixes</a></li>
+<li><a href="#bug-fixes-14" id="toc-bug-fixes-14">Bug fixes</a></li>
</ul></li>
<li><a href="#d-20190106"
id="toc-d-20190106"><code>1.3d (2019/01/06)</code></a>
@@ -292,7 +301,7 @@ changes</a></li>
<li><a href="#improvements-and-new-features-3"
id="toc-improvements-and-new-features-3">Improvements and new
features</a></li>
-<li><a href="#bug-fixes-14" id="toc-bug-fixes-14">Bug fixes</a></li>
+<li><a href="#bug-fixes-15" id="toc-bug-fixes-15">Bug fixes</a></li>
</ul></li>
<li><a href="#c-20180617"
id="toc-c-20180617"><code>1.3c (2018/06/17)</code></a>
@@ -300,7 +309,7 @@ id="toc-c-20180617"><code>1.3c (2018/06/17)</code></a>
<li><a href="#improvements-and-new-features-4"
id="toc-improvements-and-new-features-4">Improvements and new
features</a></li>
-<li><a href="#bug-fixes-15" id="toc-bug-fixes-15">Bug fixes</a></li>
+<li><a href="#bug-fixes-16" id="toc-bug-fixes-16">Bug fixes</a></li>
</ul></li>
<li><a href="#b-20180518"
id="toc-b-20180518"><code>1.3b (2018/05/18)</code></a>
@@ -316,7 +325,7 @@ id="toc-a-20180307"><code>1.3a (2018/03/07)</code></a>
<li><a href="#improvements-and-new-features-6"
id="toc-improvements-and-new-features-6">Improvements and new
features</a></li>
-<li><a href="#bug-fixes-16" id="toc-bug-fixes-16">Bug fixes</a></li>
+<li><a href="#bug-fixes-17" id="toc-bug-fixes-17">Bug fixes</a></li>
</ul></li>
<li><a href="#section-1"
id="toc-section-1"><code>1.3 (2018/03/01)</code></a>
@@ -333,7 +342,7 @@ id="toc-q-20180206"><code>1.2q (2018/02/06)</code></a>
<li><a href="#improvements-and-new-features-8"
id="toc-improvements-and-new-features-8">Improvements and new
features</a></li>
-<li><a href="#bug-fixes-17" id="toc-bug-fixes-17">Bug fixes</a></li>
+<li><a href="#bug-fixes-18" id="toc-bug-fixes-18">Bug fixes</a></li>
</ul></li>
<li><a href="#p-20171205"
id="toc-p-20171205"><code>1.2p (2017/12/05)</code></a>
@@ -343,7 +352,7 @@ changes</a></li>
<li><a href="#improvements-and-new-features-9"
id="toc-improvements-and-new-features-9">Improvements and new
features</a></li>
-<li><a href="#bug-fixes-18" id="toc-bug-fixes-18">Bug fixes</a></li>
+<li><a href="#bug-fixes-19" id="toc-bug-fixes-19">Bug fixes</a></li>
</ul></li>
<li><a href="#o-20170829"
id="toc-o-20170829"><code>1.2o (2017/08/29)</code></a>
@@ -369,7 +378,7 @@ changes</a></li>
<li><a href="#improvements-and-new-features-11"
id="toc-improvements-and-new-features-11">Improvements and new
features</a></li>
-<li><a href="#bug-fixes-19" id="toc-bug-fixes-19">Bug fixes</a></li>
+<li><a href="#bug-fixes-20" id="toc-bug-fixes-20">Bug fixes</a></li>
</ul></li>
<li><a href="#l-20170726"
id="toc-l-20170726"><code>1.2l (2017/07/26)</code></a>
@@ -378,7 +387,7 @@ id="toc-l-20170726"><code>1.2l (2017/07/26)</code></a>
<li><a href="#improvements-and-new-features-12"
id="toc-improvements-and-new-features-12">Improvements and new
features</a></li>
-<li><a href="#bug-fixes-20" id="toc-bug-fixes-20">Bug fixes</a></li>
+<li><a href="#bug-fixes-21" id="toc-bug-fixes-21">Bug fixes</a></li>
</ul></li>
<li><a href="#k-20170106"
id="toc-k-20170106"><code>1.2k (2017/01/06)</code></a>
@@ -388,7 +397,7 @@ changes</a></li>
<li><a href="#improvements-and-new-features-13"
id="toc-improvements-and-new-features-13">Improvements and new
features</a></li>
-<li><a href="#bug-fixes-21" id="toc-bug-fixes-21">Bug fixes</a></li>
+<li><a href="#bug-fixes-22" id="toc-bug-fixes-22">Bug fixes</a></li>
</ul></li>
<li><a href="#j-20161222"
id="toc-j-20161222"><code>1.2j (2016/12/22)</code></a>
@@ -396,7 +405,7 @@ id="toc-j-20161222"><code>1.2j (2016/12/22)</code></a>
<li><a href="#improvements-and-new-features-14"
id="toc-improvements-and-new-features-14">Improvements and new
features</a></li>
-<li><a href="#bug-fixes-22" id="toc-bug-fixes-22">Bug fixes</a></li>
+<li><a href="#bug-fixes-23" id="toc-bug-fixes-23">Bug fixes</a></li>
</ul></li>
<li><a href="#i-20161213"
id="toc-i-20161213"><code>1.2i (2016/12/13)</code></a>
@@ -407,7 +416,7 @@ changes</a></li>
<li><a href="#improvements-and-new-features-15"
id="toc-improvements-and-new-features-15">Improvements and new
features</a></li>
-<li><a href="#bug-fixes-23" id="toc-bug-fixes-23">Bug fixes</a></li>
+<li><a href="#bug-fixes-24" id="toc-bug-fixes-24">Bug fixes</a></li>
</ul></li>
<li><a href="#h-20161120"
id="toc-h-20161120"><code>1.2h (2016/11/20)</code></a>
@@ -415,7 +424,7 @@ id="toc-h-20161120"><code>1.2h (2016/11/20)</code></a>
<li><a href="#improvements-and-new-features-16"
id="toc-improvements-and-new-features-16">Improvements and new
features</a></li>
-<li><a href="#bug-fixes-24" id="toc-bug-fixes-24">Bug fixes</a></li>
+<li><a href="#bug-fixes-25" id="toc-bug-fixes-25">Bug fixes</a></li>
</ul></li>
<li><a href="#g-20160319"
id="toc-g-20160319"><code>1.2g (2016/03/19)</code></a>
@@ -434,7 +443,7 @@ changes</a></li>
<li><a href="#improvements-and-new-features-18"
id="toc-improvements-and-new-features-18">Improvements and new
features</a></li>
-<li><a href="#bug-fixes-25" id="toc-bug-fixes-25">Bug fixes</a></li>
+<li><a href="#bug-fixes-26" id="toc-bug-fixes-26">Bug fixes</a></li>
</ul></li>
<li><a href="#e-20151122"
id="toc-e-20151122"><code>1.2e (2015/11/22)</code></a>
@@ -442,7 +451,7 @@ id="toc-e-20151122"><code>1.2e (2015/11/22)</code></a>
<li><a href="#improvements-and-new-features-19"
id="toc-improvements-and-new-features-19">Improvements and new
features</a></li>
-<li><a href="#bug-fixes-26" id="toc-bug-fixes-26">Bug fixes</a></li>
+<li><a href="#bug-fixes-27" id="toc-bug-fixes-27">Bug fixes</a></li>
</ul></li>
<li><a href="#d-20151118"
id="toc-d-20151118"><code>1.2d (2015/11/18)</code></a>
@@ -450,7 +459,7 @@ id="toc-d-20151118"><code>1.2d (2015/11/18)</code></a>
<li><a href="#improvements-and-new-features-20"
id="toc-improvements-and-new-features-20">Improvements and new
features</a></li>
-<li><a href="#bug-fixes-27" id="toc-bug-fixes-27">Bug fixes</a></li>
+<li><a href="#bug-fixes-28" id="toc-bug-fixes-28">Bug fixes</a></li>
</ul></li>
<li><a href="#c-20151116"
id="toc-c-20151116"><code>1.2c (2015/11/16)</code></a>
@@ -458,12 +467,12 @@ id="toc-c-20151116"><code>1.2c (2015/11/16)</code></a>
<li><a href="#improvements-and-new-features-21"
id="toc-improvements-and-new-features-21">Improvements and new
features</a></li>
-<li><a href="#bug-fixes-28" id="toc-bug-fixes-28">Bug fixes</a></li>
+<li><a href="#bug-fixes-29" id="toc-bug-fixes-29">Bug fixes</a></li>
</ul></li>
<li><a href="#b-20151029"
id="toc-b-20151029"><code>1.2b (2015/10/29)</code></a>
<ul>
-<li><a href="#bug-fixes-29" id="toc-bug-fixes-29">Bug fixes</a></li>
+<li><a href="#bug-fixes-30" id="toc-bug-fixes-30">Bug fixes</a></li>
</ul></li>
<li><a href="#a-20151019"
id="toc-a-20151019"><code>1.2a (2015/10/19)</code></a>
@@ -471,7 +480,7 @@ id="toc-a-20151019"><code>1.2a (2015/10/19)</code></a>
<li><a href="#improvements-and-new-features-22"
id="toc-improvements-and-new-features-22">Improvements and new
features</a></li>
-<li><a href="#bug-fixes-30" id="toc-bug-fixes-30">Bug fixes</a></li>
+<li><a href="#bug-fixes-31" id="toc-bug-fixes-31">Bug fixes</a></li>
</ul></li>
<li><a href="#section-2"
id="toc-section-2"><code>1.2 (2015/10/10)</code></a>
@@ -497,7 +506,7 @@ changes</a></li>
<li><a href="#improvements-and-new-features-24"
id="toc-improvements-and-new-features-24">Improvements and new
features</a></li>
-<li><a href="#bug-fixes-31" id="toc-bug-fixes-31">Bug fixes</a></li>
+<li><a href="#bug-fixes-32" id="toc-bug-fixes-32">Bug fixes</a></li>
</ul></li>
<li><a href="#n-20140401"
id="toc-n-20140401"><code>1.09n (2014/04/01)</code></a></li>
@@ -549,17 +558,68 @@ id="toc-section-9"><code>1.03 (2013/04/14)</code></a></li>
id="toc-section-10"><code>1.0 (2013/03/28)</code></a></li>
</ul>
</nav>
-<pre><code>Source: xint.dtx 1.4k 2022/05/18 (doc 2022/05/18)
+<pre><code>Source: xint.dtx 1.4l 2022/05/29 (doc 2022/05/29)
Author: Jean-Francois Burnol
Info: Expandable operations on big integers, decimals, fractions
License: LPPL 1.3c</code></pre>
+<h2 id="l-20220529"><code>1.4l (2022/05/29)</code></h2>
+<h3 id="bug-fixes">Bug fixes</h3>
+<ul>
+<li><p><strong>xintkernel</strong>: ever since <code>1.4</code>, loading
+anyone of the <code>xint*sty</code> packages left the catcode of the
+character of ascii code <code>1</code> to the internal custom value
+<code>3</code>.</p></li>
+<li><p><strong>xintfrac</strong>: the <code>\xintPFloat</code> checks
+for an output being an integer in decimal notation or a number with a
+one-digit trimmed mantissa could fail if
+<code>\xintPFloatMinTrimmed</code> (added at <code>1.4k</code>) was
+large enough, e.g. equal to the target precision. Then, the outputs
+always kept trailing zeros, as expected in general but not for those
+special cases.</p></li>
+<li><p><strong>xintlog</strong>, <strong>xinttrig</strong>: since
+<code>1.4e</code> the message emitted if
+<code>\usepackage{xintlog}</code> or <code>\usepackage{xinttrig}</code>
+was encountered in place of the correct
+<code>\usepackage{xintexpr}</code> was wrong. It advised to use
+<code>\input xintexpr.sty\relax</code>, which would have failed with
+LaTeX. The warning is corrected and now the macro file in place of
+aborting will (be it with or without LaTeX) trigger the loading of
+<code>xintexpr</code> (hence of itself after it).</p></li>
+<li><p>The possibility to run <code>latex</code> directly on
+<code>xint.dtx</code> had been broken since <code>1.4i</code>.</p></li>
+</ul>
+<h3 id="new-features">New features</h3>
+<ul>
+<li><p><strong>xintfrac</strong>: <code>\xintRawBraced</code> as a
+public alias to an <strong>xintfrac</strong> entry point to its core
+input handler. Experimental additions <code>\xintSignBit</code> and
+<code>\xintFloatBraced</code>. Deprecate <code>\xintTeXfromSci</code> in
+favor of new name <code>\xintTeXFromSci</code>, and remove its
+<code>\expanded</code> wrapper (so it is not f-expandable anymore). Add
+<code>\xintTeXFromScifracmacro</code>.</p></li>
+<li><p><strong>xintfrac</strong>, <strong>xintexpr</strong>:
+<code>\xintFracToSci</code> and <code>\xintFracToDecimal</code> now
+behave like all other <strong>xintfrac</strong> macros in terms of
+allowed arguments and f-expandability and have been moved back to
+<strong>xintfrac</strong>.</p></li>
+</ul>
+<h3 id="documentation">Documentation</h3>
+<ul>
+<li><p>Renewed random shuffling of large parts of the documentation has
+greatly improved it.</p></li>
+<li><p>Simpler build flow to produce a <code>pdf</code> containing both
+user manual and source code. Removal of dependency on <code>grep</code>
+binary for such builds or the one of <code>sourcexint.pdf</code>. Fix of
+various obsoleted comments in extracted files involved in the
+documentation build process.</p></li>
+</ul>
<h2 id="k-20220518"><code>1.4k (2022/05/18)</code></h2>
<h3 id="breaking-changes">Breaking changes</h3>
<ul>
<li><p><strong>xintfrac</strong>: the longstanding (but documented as
undecided and unstable) way of <code>\xintFloat</code> to output the
zero value was <code>0.e0</code> and it has now been modified into
-<code>0.0e0</code>. Customizable via
+<code>0.0e0</code>. Now customizable via
<code>\xintFloatZero</code>.</p></li>
<li><p><strong>xintfrac</strong>/<strong>xintexpr</strong>: the
behaviour of <code>\xintPFloat</code> (hence of
@@ -572,17 +632,17 @@ with a single-digit (trimmed) mantissa, no <code>.0</code> is used.</p>
<code>\xintPFloatLengthOneSuffix</code>, and
<code>\xintPFloatZero</code>.</p>
<p>Also, <code>\xintPFloat</code> trims trailing zeros from the full
-significand only if there are at least <code>4</code> of them, see
-<code>\xintPFloatMinTrimmed</code>.</p></li>
-<li><p><strong>xintfrac</strong>/<strong>xintexpr</strong>: definition
-of <code>\xintFracToSci</code> migrated from the former to the
-latter.</p></li>
+significand only if there are, by default, at least <code>4</code> of
+them, see <code>\xintPFloatMinTrimmed</code>.</p></li>
+<li><p><strong>xintfrac</strong>/<strong>xintexpr</strong>: macro
+definition of <code>\xintFracToSci</code> migrated from the former to
+the latter (see <code>1.4l</code> for update).</p></li>
<li><p><strong>xintexpr</strong>:
<code>\xintexpr{Safe,Restore}Catcodes</code> pairs now behave like a
“last in first out” stack. Check the <code>pdf</code> documentation for
details.</p></li>
</ul>
-<h3 id="bug-fixes">Bug fixes</h3>
+<h3 id="bug-fixes-1">Bug fixes</h3>
<ul>
<li><p><strong>xintexpr</strong>: the
<code>\xintexpr{Safe,Restore}Catcodes</code> were documented at user
@@ -596,7 +656,7 @@ modified).</p></li>
reset the catcodes to their status prior to the sanitization done by the
macro at the start of its execution.</p></li>
</ul>
-<h3 id="new-features">New features</h3>
+<h3 id="new-features-1">New features</h3>
<ul>
<li><p><strong>xintfrac</strong>: <code>\xintPFloatZero</code>,
<code>\xintPFloatIntSuffix</code>,
@@ -609,7 +669,7 @@ expression). Also added <code>\xintFloatZero</code>.</p></li>
<li><p><strong>xintfrac</strong>:
<code>\xintFloatToDecimal</code>.</p></li>
<li><p><strong>xintexpr</strong>: <code>\xintFracToDecimal</code>, an
-alternative to <code>\xintFracToSci</code> for the configuration of
+alternative to the default <code>\xintFracToSci</code> configuration of
<code>\xintexprPrintOne</code>.</p></li>
<li><p><strong>xintexpr</strong>: long awaited syntax
<code>\xintieval[D]{...}</code> and <code>\xintfloateval[Q]{...}</code>
@@ -618,7 +678,7 @@ and <code>\xintfloateval{[Q]...}</code> is kept for backwards
compatibility.</p></li>
</ul>
<h2 id="j-20210713"><code>1.4j (2021/07/13)</code></h2>
-<h3 id="bug-fixes-1">Bug fixes</h3>
+<h3 id="bug-fixes-2">Bug fixes</h3>
<ul>
<li><strong>xinttools</strong>: a brace removal bug affected the
venerable <code>\xintSeq</code> if producing a single number
@@ -626,7 +686,7 @@ venerable <code>\xintSeq</code> if producing a single number
<code>{10}</code>). Thanks to Christophe Poulain for report.</li>
</ul>
<h2 id="i-20210611"><code>1.4i (2021/06/11)</code></h2>
-<h3 id="new-features-1">New features</h3>
+<h3 id="new-features-2">New features</h3>
<ul>
<li><p><strong>xintexpr</strong>: the concept of simultaneous
assignments is extended: in case of more variables than values the
@@ -641,7 +701,7 @@ single numeric argument: since <code>1.4</code> a lone argument had to
be a <code>nutple</code> (which was automatically unpacked). It can now
again be a number.</p></li>
</ul>
-<h3 id="bug-fixes-2">Bug fixes</h3>
+<h3 id="bug-fixes-3">Bug fixes</h3>
<ul>
<li><p><strong>xintexpr</strong>: simultaneous assignments via
<code>\xintdefvar</code> to 10 or more variables was broken if the right
@@ -662,7 +722,7 @@ variables (currently <code>subs()</code>, <code>subsm()</code>,
<code>seq</code>.</p></li>
</ul>
<h2 id="h-20210527"><code>1.4h (2021/05/27)</code></h2>
-<h3 id="bug-fixes-3">Bug fixes</h3>
+<h3 id="bug-fixes-4">Bug fixes</h3>
<ul>
<li><p><strong>xintexpr</strong>: the recent <code>1.4g</code>
introduced a bug breaking input of the type
@@ -697,7 +757,7 @@ way: <code>2^3^4==2^(3^4)</code>.</p></li>
<code>\xintTeXOver</code>, <code>\xintTeXsignedOver</code>. The old
names will emit warnings.</li>
</ul>
-<h3 id="new-features-2">New features</h3>
+<h3 id="new-features-3">New features</h3>
<ul>
<li><p>Messages written to the terminal and log file during the handling
of recovery from exceptions use a new mechanism; when in interactive
@@ -709,7 +769,7 @@ about 7 or 8 years too late) to help typesetting values output by
<code>\xintfloateval</code> in a more useful way than
<code>\xintTeXFrac</code> (formerly <code>\xintFrac</code>).</p></li>
</ul>
-<h3 id="bug-fixes-4">Bug fixes</h3>
+<h3 id="bug-fixes-5">Bug fixes</h3>
<ul>
<li><p><strong>xintexpr</strong>: with <strong>xintbinhex</strong>
loaded, <code>"</code> is recognized as prefix for hexadecimal input;
@@ -777,7 +837,7 @@ powers, see the bug fixes below.</p></li>
<li><p><strong>xintexpr</strong>: the <code>float_()</code> function got
renamed into <code>float_dgt()</code>.</p></li>
</ul>
-<h3 id="bug-fixes-5">Bug fixes</h3>
+<h3 id="bug-fixes-6">Bug fixes</h3>
<ul>
<li><p><strong>xintexpr</strong>: the documentation said
<code>float_()</code> function had been renamed <code>float_dgt()</code>
@@ -863,7 +923,7 @@ pre-rounding to the Digits precision.</p></li>
over the process to <code>\xintPFloat</code> (without the rounding to
Digits, of course).</p></li>
</ul>
-<h3 id="new-features-3">New features</h3>
+<h3 id="new-features-4">New features</h3>
<ul>
<li><p><strong>xintlog</strong>: now working up to <code>62</code>
digits. The legacy faster <code>poormanlog</code>-based macros are kept
@@ -888,7 +948,7 @@ the letter <code>e</code>.</p></li>
like <code>\xintDecToString</code> but starts by removing trailing
zeroes.</p></li>
</ul>
-<h3 id="bug-fixes-6">Bug fixes</h3>
+<h3 id="bug-fixes-7">Bug fixes</h3>
<ul>
<li><strong>xintfrac</strong>, <strong>xintexpr</strong>: it was not
possible to use <code>\xinttheDigits</code> in the right hand side of an
@@ -910,7 +970,7 @@ applied to fractions is now always in lowest terms.</p></li>
around the name. By the way, quotes were never used for function
names.</p></li>
</ul>
-<h3 id="bug-fixes-7">Bug fixes</h3>
+<h3 id="bug-fixes-8">Bug fixes</h3>
<ul>
<li><p>Ever since <code>1.3</code> the <code>quo()</code> and
<code>rem()</code> functions in <code>\xintexpr</code> (not the ones in
@@ -935,7 +995,7 @@ inside an <code>\xintdeffunc</code> caused the defined function to be
broken.</p></li>
</ul>
<h2 id="c-20210220"><code>1.4c (2021/02/20)</code></h2>
-<h3 id="bug-fixes-8">Bug fixes</h3>
+<h3 id="bug-fixes-9">Bug fixes</h3>
<ul>
<li>Fix <code>1.4</code> regression which broke syntax
<code>varname(...)</code> which supposedly is allowed and inserts a
@@ -960,7 +1020,7 @@ so much better names. Besides, since <code>1.4</code>,
<code>\xintexpr</code> can be used directly in typesetting
flow.</p></li>
</ul>
-<h3 id="new-features-4">New features</h3>
+<h3 id="new-features-5">New features</h3>
<ul>
<li><p>Function <code>zip()</code> is modeled on Python’s function of
the same name.</p></li>
@@ -977,7 +1037,7 @@ strangely there was no way to customize the output of
<code>\xintfloateval</code>. The added <code>\xintPFloatE</code> fixes
this.</p></li>
</ul>
-<h3 id="bug-fixes-9">Bug fixes</h3>
+<h3 id="bug-fixes-10">Bug fixes</h3>
<ul>
<li><code>\xintieval{[D]...}</code> with a negative <code>D</code> (a
feature added at <code>1.4a</code>) used erroneously a catcode 12
@@ -991,7 +1051,7 @@ feature added at <code>1.4a</code>) used erroneously a catcode 12
<li>The macros implementing customization of <code>\xintthealign</code>
have modified meanings and names.</li>
</ul>
-<h3 id="new-features-5">New features</h3>
+<h3 id="new-features-6">New features</h3>
<ul>
<li><p><code>\xintthespaceseparated</code> (serves to provide suitable
input to PS-Tricks <code>\listplot</code>).</p></li>
@@ -1004,7 +1064,7 @@ of <code>10^(-D)</code>.</p>
<code>\xintRound</code>, <code>\xintiTrunc</code>, and
<code>\xintiRound</code> macros of <strong>xintfrac</strong>.</p></li>
</ul>
-<h3 id="bug-fixes-10">Bug fixes</h3>
+<h3 id="bug-fixes-11">Bug fixes</h3>
<ul>
<li><p>Usage of <code>round()</code> and <code>trunc()</code> within
<code>\xintdeffunc</code> got broken at <code>1.4</code>.</p></li>
@@ -1234,7 +1294,7 @@ example a correct variable or function name in place of the not
recognized one. But don’t expect miracles when trying to intervene in
the midst of a purely expandable expansion…</p></li>
</ul>
-<h3 id="bug-fixes-11">Bug fixes</h3>
+<h3 id="bug-fixes-12">Bug fixes</h3>
<p>Bugs? Those identified in <code>1.3f</code> were almost features. As
per <code>1.4</code> the code base of <strong>xintexpr</strong> received
multiple successive core refactorings and added numerous new features,
@@ -1271,7 +1331,7 @@ token e.g. <code>\xintDigits := 32\relax</code>.</p>
expressions by <code>\xintdeffunc</code>. And make them usable also
inside macro definitions via <code>\xintNewExpr</code>.</p></li>
</ul>
-<h3 id="bug-fixes-12">Bug fixes</h3>
+<h3 id="bug-fixes-13">Bug fixes</h3>
<ul>
<li><p><strong>xintexpr</strong>: fix bug preventing usage of
<code>\xintdefefunc</code> to define a function without variables.</p>
@@ -1318,7 +1378,7 @@ shortcomings.</p></li>
be negative; it then means to trim (and round) from the output at float
precision that many least significant digits.</p></li>
</ul>
-<h3 id="bug-fixes-13">Bug fixes</h3>
+<h3 id="bug-fixes-14">Bug fixes</h3>
<ul>
<li>Some bugfixes related to user functions with no variables at all;
they were dysfunctional.</li>
@@ -1361,7 +1421,7 @@ value zero),</p></li>
<code>\xinttheexpr...\relax</code> etc…, but with the (comma-separated)
expression as a usual braced macro argument.</p></li>
</ul>
-<h3 id="bug-fixes-14">Bug fixes</h3>
+<h3 id="bug-fixes-15">Bug fixes</h3>
<ul>
<li><strong>xintcore</strong>, <strong>xintexpr</strong> : division in
<code>\xintiiexpr</code> was broken for a zero dividend and a one-digit
@@ -1393,7 +1453,7 @@ work if that catcode is already frozen.</p></li>
<code>sourcexint.pdf</code> is better hyperlinked and includes indices
for the macros defined by each package.</p></li>
</ul>
-<h3 id="bug-fixes-15">Bug fixes</h3>
+<h3 id="bug-fixes-16">Bug fixes</h3>
<ul>
<li><strong>xintfrac</strong>: since <code>1.3</code> release, it loaded
<strong>xintgcd</strong> in contradiction to what the documentation says
@@ -1444,7 +1504,7 @@ inputs having one hundred digits or more.</p></li>
<code>\xintDivFloor</code>, <code>\xintMod</code>,
<code>\xintModTrunc</code>, which had been left out so far.</p></li>
</ul>
-<h3 id="bug-fixes-16">Bug fixes</h3>
+<h3 id="bug-fixes-17">Bug fixes</h3>
<ul>
<li><strong>xintexpr</strong>: the mechanism for adjunction to the
expression parsers of user defined functions was refactored and improved
@@ -1495,7 +1555,7 @@ features</h3>
<li><strong>xintexpr</strong>: tacit multiplication extended to cases
such as <code>3!4!5!</code> or <code>(1+2)3</code>.</li>
</ul>
-<h3 id="bug-fixes-17">Bug fixes</h3>
+<h3 id="bug-fixes-18">Bug fixes</h3>
<ul>
<li><strong>xintcore</strong>: sadly, refactoring at <code>1.2l</code>
of subtraction left an extra character in an inner macro causing
@@ -1543,7 +1603,7 @@ built-in functions. It is associated with floored division, like the
Python language <code>divmod()</code>. Related support macros added to
<strong>xintcore</strong>, and <strong>xintfrac</strong>.</p></li>
</ul>
-<h3 id="bug-fixes-18">Bug fixes</h3>
+<h3 id="bug-fixes-19">Bug fixes</h3>
<ul>
<li><p><strong>xintgcd</strong>: <code>\xintBezout{6}{3}</code> (for
example) expanded to <code>{6}{3}{-0}{-1}{3}</code>, but the
@@ -1656,7 +1716,7 @@ but limited to a few thousand digits. The <code>1.08</code> routines
could handle tens of thousands of digits, but not in a reasonable
time.</li>
</ul>
-<h3 id="bug-fixes-19">Bug fixes</h3>
+<h3 id="bug-fixes-20">Bug fixes</h3>
<ul>
<li><p>user manual: the <code>Changes</code> section wrongly stated at
<code>1.2l</code> that the macros of <strong>xintbinhex</strong> had
@@ -1725,7 +1785,7 @@ in this example a second <code>\relax</code>.</p></li>
interface yet, it is done in preparation for next major release and is
completely unstable and undocumented.</p></li>
</ul>
-<h3 id="bug-fixes-20">Bug fixes</h3>
+<h3 id="bug-fixes-21">Bug fixes</h3>
<ul>
<li><p><strong>xintbinhex</strong>: since <code>1.2 (2015/10/10)</code>,
<code>\xintHexToDec</code> was broken due to an undefined macro (it was
@@ -1784,7 +1844,7 @@ variables.)</p></li>
improved <code>\xintNewExpr</code> compatibility. Also
<code>\xintFirstItem:f:csv</code>.</p></li>
</ul>
-<h3 id="bug-fixes-21">Bug fixes</h3>
+<h3 id="bug-fixes-22">Bug fixes</h3>
<ul>
<li><p>the <code>1.2f</code> half-integer powers computed within
<code>\xintfloatexpr</code> had a silly rounding to the target precision
@@ -1823,7 +1883,7 @@ horizontal and vertical rules which bring the documentation of the
except that implementation of some math functions is still
lacking.</p></li>
</ul>
-<h3 id="bug-fixes-22">Bug fixes</h3>
+<h3 id="bug-fixes-23">Bug fixes</h3>
<ul>
<li>fix two <code>1.2i</code> regressions caused by undefined macros
(<code>\xintNthElt</code> in certain branches and <code>[list][N]</code>
@@ -1893,7 +1953,7 @@ should have been removed long ago) and uses only the more apt “macro”,
as after all, all of <strong>xint</strong> is about expansion of macros
(plus the use of <code>\numexpr</code>).</p></li>
</ul>
-<h3 id="bug-fixes-23">Bug fixes</h3>
+<h3 id="bug-fixes-24">Bug fixes</h3>
<ul>
<li><code>\xintDecSplitL</code> and <code>\xintDecSplitR</code> from
<strong>xint</strong> produced their output in a spurious brace pair
@@ -1913,7 +1973,7 @@ prefix, now <code>\thexintexpr</code>, <code>\thexintiexpr</code>,
<code>\thexintfloatexpr</code>, and <code>\thexintiiexpr</code> are
provided as synonyms to <code>\xinttheexpr</code>, etc…</p></li>
</ul>
-<h3 id="bug-fixes-24">Bug fixes</h3>
+<h3 id="bug-fixes-25">Bug fixes</h3>
<ul>
<li><p>the <code>(cond)?{foo}{bar}</code> operator from
<strong>xintexpr</strong> mis-behaved in certain circumstances (such as
@@ -2026,7 +2086,7 @@ initial <code>\romannumeral</code> anymore.</p></li>
random shuffling of sections and well thought additions; cuts were
considered and even performed.</p></li>
</ul>
-<h3 id="bug-fixes-25">Bug fixes</h3>
+<h3 id="bug-fixes-26">Bug fixes</h3>
<ul>
<li><p>squaring macro <code>\xintSqr</code> from
<strong>xintfrac.sty</strong> was broken due to a misspelled sub-macro
@@ -2056,7 +2116,7 @@ its included code samples has been entirely re-written; the <em>Commands
of the xintexpr package</em> section has been extended and reviewed
entirely.</p></li>
</ul>
-<h3 id="bug-fixes-26">Bug fixes</h3>
+<h3 id="bug-fixes-27">Bug fixes</h3>
<ul>
<li><p>in <strong>xintfrac</strong>: the <code>\xintFloatFac</code> from
release <code>1.2</code> parsed its argument only through
@@ -2082,7 +2142,7 @@ x/(2*y).</p></li>
<li><p>some documentation enhancements, particularly in the chapter on
xintexpr.sty, and also in the code source comments.</p></li>
</ul>
-<h3 id="bug-fixes-27">Bug fixes</h3>
+<h3 id="bug-fixes-28">Bug fixes</h3>
<ul>
<li>in <strong>xintcore</strong>: release <code>1.2c</code> had
inadvertently broken the <code>\xintiiDivRound</code> macro.</li>
@@ -2097,14 +2157,14 @@ features</h3>
<li><p>on-going code improvements and documentation enhancements, but
stopped in order to issue this bugfix release.</p></li>
</ul>
-<h3 id="bug-fixes-28">Bug fixes</h3>
+<h3 id="bug-fixes-29">Bug fixes</h3>
<ul>
<li>in <strong>xintcore</strong>: recent release <code>1.2</code>
introduced a bug in the subtraction (happened when 00000001 was found
under certain circumstances at certain mod 8 locations).</li>
</ul>
<h2 id="b-20151029"><code>1.2b (2015/10/29)</code></h2>
-<h3 id="bug-fixes-29">Bug fixes</h3>
+<h3 id="bug-fixes-30">Bug fixes</h3>
<ul>
<li>in <strong>xintcore</strong>: recent release <code>1.2</code>
introduced a bug in the division macros, causing a crash when the
@@ -2126,7 +2186,7 @@ regarding brace stripping.</p></li>
<code>\romannumeral`&amp;&amp;@</code> (<code>^</code> being used as
letter, had to find another character usable with catcode 7).</p></li>
</ul>
-<h3 id="bug-fixes-30">Bug fixes</h3>
+<h3 id="bug-fixes-31">Bug fixes</h3>
<ul>
<li>in <strong>xintexpr</strong>: recent release <code>1.2</code>
introduced a bad bug in the parsing of decimal numbers and as a result
@@ -2409,7 +2469,7 @@ even number of items to the format expected by the <code>TikZ</code>
standard macro parameter <code>#</code>. Not all constructs are
compatible with <code>\xintNewExpr</code>.</p></li>
</ul>
-<h3 id="bug-fixes-31">Bug fixes</h3>
+<h3 id="bug-fixes-32">Bug fixes</h3>
<ul>
<li><p><code>\xintZapFirstSpaces</code> hence also
<code>\xintZapSpaces</code> from package <strong>xinttools</strong> were