ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Philipp Gesang <pgesang@ix.urz.uni-heidelberg.de>
Subject: Re: why lua?
Date: Sat, 18 Dec 2010 12:31:42 +0100	[thread overview]
Message-ID: <4D0C9B9E.1030104@elvenkind.com> (raw)
In-Reply-To: <AANLkTinNw0J0eNco5XME0hBofXyXMJ+8WKARy3Wbnuyc@mail.gmail.com>


Hi,

On 12/18/2010 01:50 AM, Philipp A. wrote:
>
> like… which one? i only know of the tabs vs. spaces

The significant whitespace is why python would not have been
an option for the core extension language in luatex even if
it was twice as small and twice as fast as lua. Forced indentation
simply does not work out well if data and program are intermixed
in the same source file.

Which is not saying that I don't like python, but (also taking account
the other differences to lua) it is simply the wrong tool for the job.

> my dream for luatex/context would be a built-in lua interpreter (because
> lua is so fucking small) and optional modules for other, heavier,
> scripting languages (perl, ruby), which you don’t have to install.

An extended version of luatex-lunatic (or some similar project) would
potentially allow that. A lot of the lua functions that 'talk' to the
internals are nothing more than wrappers for argument and return value
grabbing, and it would be pretty easy to (re)code those bindings for
any other scripting language.

The remaining functions that are not trivially implemented are the
ones that we need to work on before 1.0, because these are the exactly
the areas where the TeX source is too messy to be easily interfaced,
in any scripting language.


Best wishes,
Taco
___________________________________________________________________________________
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
___________________________________________________________________________________

  parent reply	other threads:[~2010-12-18 11:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-17 15:20 Jonas Stein
2010-12-17 21:46 ` Martin Schröder
2010-12-17 22:35 ` Philipp A.
2010-12-17 22:51   ` Hans Hagen
2010-12-18  8:35     ` luigi scarso
2010-12-17 22:48 ` Hans Hagen
2010-12-17 23:27 ` Philipp Gesang
2010-12-17 23:46   ` Hans Hagen
2010-12-18  0:50     ` Philipp A.
2010-12-18  5:56       ` Aditya Mahajan
2010-12-18 11:03       ` Philipp Gesang
2010-12-18 11:35         ` Hans Hagen
2010-12-18 13:06           ` Philipp Gesang
2010-12-18 13:20             ` Hans Hagen
2010-12-18 14:17               ` Philipp Gesang
2010-12-18 18:54                 ` Hans Hagen
2010-12-18 11:31       ` Taco Hoekwater [this message]
2010-12-18 13:04       ` Hans Hagen
2010-12-18 13:18         ` luigi scarso
2010-12-18 13:24           ` Hans Hagen

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=4D0C9B9E.1030104@elvenkind.com \
    --to=taco@elvenkind.com \
    --cc=ntg-context@ntg.nl \
    --cc=pgesang@ix.urz.uni-heidelberg.de \
    /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).