ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Ctx & Lua 5.3
Date: Wed, 28 May 2014 13:47:59 +0200	[thread overview]
Message-ID: <5385CCEF.7070907@wxs.nl> (raw)
In-Reply-To: <op.xgkci0ngtpjj8f@lpr>

On 5/28/2014 11:26 AM, Procházka Lukáš Ing. - Pontex s. r. o. wrote:
> Hello,
>
> On Sun, 25 May 2014 18:33:59 +0200, Hans Hagen <pragma@wxs.nl> wrote:
>
>> On 5/25/2014 1:33 PM, Lukáš Procházka wrote:
>>
>>> - Question: when is Ctx supposed to adopt Lua 5.3?
>>
>> It will take a while as
>>
>> - 5.3 it's not yet official
>> - then 5.3 needs to become stable
>> - we need to test implications of the new number system
>> - tests have shows it's a slightly slower
>>
>> Maybe there's nothing to gain from a move to 5.3, apart from keeping up
>> with general Lua. If we make the switch it will first be tested quite a
>> while in production before it leaves beta.
>
> OK.
>
> Did you think about Ctx be able to use more Lua versions?
>
> Similar like "--jit" forces LuaJIT instead of Lua;
> "--lua52" would force Lua 5.2 instead Lua 5.3+ once Lua 5.3+ is adopted
> into Ctx core (and supposing Ctx won't use any Lua 5.3+ extras).

unlikely ... i can think of more interesting things to do than spending 
the free time i've left to coding for multiple lua dialects, so if we 
move to 5.3 and i want to use its new features, 5.2 is no longer assumed 
and supported (one thing i can think of is bitwise operators)

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


      reply	other threads:[~2014-05-28 11:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23 10:40 Ctx goes into infinite loop? Procházka Lukáš Ing. - Pontex s. r. o.
2014-05-23 11:15 ` Hans Hagen
2014-05-23 11:30   ` Procházka Lukáš Ing. - Pontex s. r. o.
2014-05-23 11:50     ` Hans Hagen
2014-05-23 14:18       ` Peter Rolf
2014-05-23 16:01         ` Peter Rolf
2014-05-25 11:33         ` Lukáš Procházka
2014-05-25 16:33           ` Hans Hagen
2014-05-28  9:26             ` Ctx & Lua 5.3 (was: Ctx goes into infinite loop?) Procházka Lukáš Ing. - Pontex s. r. o.
2014-05-28 11:47               ` Hans Hagen [this message]

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=5385CCEF.7070907@wxs.nl \
    --to=pragma@wxs.nl \
    --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).