From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
"General discussion of LuaTeX." <luatex@tug.org>,
luatex development list <dev-luatex@ntg.nl>,
Dev Context <dev-context@ntg.nl>
Subject: Luatex 1.07.0 announcement
Date: Thu, 19 Apr 2018 13:48:31 +0200 [thread overview]
Message-ID: <CAG5iGsDkTt7K1rcczhY7_8D3gcDO8+eh=rm7FZ+3y5Byv4+bbg@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1808 bytes --]
==============================================================
LuaTeX 1.07 2018-01-17
==============================================================
(1) This release brings Lua 5.3 to LuaTeX. We have tested an experimental
version
for a few months and not encountered issues.
(2) If you use Lua 5.3 you should be aware of a few changes in the language
and
its implementation. Numbers are now either integers or floats but are cast
automatically.
(3) In some cases (e.g. string.format) there is a more strict check. A
float always
has a decimal appended when serialized, so 1 becomes 1.0 as string.
(4) We keep supporting the bit32 library on top of the new bit operators.
Be aware
of the fact that currently LuajitTeX does not have these operators.
(5) Performance of LuaTeX with Lua 5.3 can be slightly better than with 5.2
but this
really depends on your usage of Lua. In practice there should be no
slowdown.
(6) We are aware of possible substantial slowdown of string.format
depending on the
platform and compiler. This depends on Lua too and will be resolved in due
time.
(7) If you want to test with Lua 5.3 then have to build LuaTeX with
--lua53. Because
ConTeXt will switch to 5.3 after this release there will be binaries
available at the
ConTeXt garden.
(8) The 2018 TeXlive distribution will ship with LuaTeX using Lua 5.2 but
there will
likely be an additional binary LuaTeX53 available.
(9) From 2019 TeXlive will ship with LuaTeX and Lua 5.3 as default. We
provide --lua52
as build flag for a while. By then we might be looking at Lua 5.4 already.
(10) There are the usual patches and cleanups and a few small additions
(mentioned
in the manual) but there have been no fundamental changes in the API (apart
from
removing depricated and undocumented functionality).
The LuaTeX team
[-- Attachment #1.2: Type: text/html, Size: 2335 bytes --]
[-- Attachment #2: Type: text/plain, Size: 144 bytes --]
_______________________________________________
dev-context mailing list
dev-context@ntg.nl
https://mailman.ntg.nl/mailman/listinfo/dev-context
reply other threads:[~2018-04-19 11:48 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='CAG5iGsDkTt7K1rcczhY7_8D3gcDO8+eh=rm7FZ+3y5Byv4+bbg@mail.gmail.com' \
--to=luigi.scarso@gmail.com \
--cc=dev-context@ntg.nl \
--cc=dev-luatex@ntg.nl \
--cc=luatex@tug.org \
--cc=ntg-context@ntg.nl \
/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).