ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Stephen Gaito <stephen@perceptisys.co.uk>
Subject: Re: Using ConTeXt-LMTX for modern Mathematically-Literate-Programming 2/2
Date: Wed, 2 Dec 2020 14:17:54 +0100	[thread overview]
Message-ID: <78fa9e35-40ef-3fa0-6525-2230cd817a4e@xs4all.nl> (raw)
In-Reply-To: <20201202104308.1ef6b719@nn01>

On 12/2/2020 11:43 AM, Stephen Gaito wrote:

> Again, to my knowledge, Lua v5.4 has only one implementation (though
> this implementation *can* be compiled for a very wide range of CPU's).

Lua has not many demands ... it can even run on tiny cpu's. It's all 
rather plain C code. (And in luametatex we have no c++ ... all is just C.)

> Finally, the computational complexity of my proof engine, will be
> comparable to MetaFun/MetaPost... which I suspect you would not
> consider implementing in pure Lua. Some things are faster in C.

Hard to say ... I think that the parser / expansion machinery in mp is 
the bottleneck here (no fun to do that in lua). Redoing it in Lua also 
is asking for compatibility issues. (btw, extensions are done in lua 
anyway, as is the mp backend)

> So yes I do need to implement it in ANSI-C wrapped in Lua (so that it
> can be used from *inside* ConTeXt).

I would have to see the 'kind of code involved' in order to comment on 
that.

An option is to do most in lua and maybe some helpers for crititical 
code in C.
  Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2020-12-02 13:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30  9:51 Stephen Gaito
     [not found] ` <83c1393f-f11e-9260-9593-16c6f8c42189@xs4all.nl>
2020-12-02 10:43   ` Stephen Gaito
2020-12-02 13:17     ` Hans Hagen [this message]
2020-12-03 10:43       ` Stephen Gaito

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=78fa9e35-40ef-3fa0-6525-2230cd817a4e@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=ntg-context@ntg.nl \
    --cc=stephen@perceptisys.co.uk \
    /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).