ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Hans Åberg" <haberg-1@telia.com>
To: Hans Hagen <pragma@wxs.nl>
Cc: ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Latin setupmathematics
Date: Mon, 16 May 2016 10:59:50 +0200	[thread overview]
Message-ID: <4365BE58-B85A-4B7F-81B8-C5AE92A28E6C@telia.com> (raw)
In-Reply-To: <23faace2-8dce-f956-a771-e7cea2a75128@wxs.nl>


> On 16 May 2016, at 10:48, Hans Hagen <pragma@wxs.nl> wrote:

>>> interesting tex was flexible enough to survive many decades
>> 
>> Other survivors are C, C++, Scheme. With TeX, change may start as with Lua, only some better syntax for text input.
> 
> that always depend on the content; for complex docs tex or xml is ok (and best)

The TeX syntax is too loose to do input that is close to the input. For example, in math, if properly parsed, the "{…}” can often be replaced by the normal “(…)”, and the the engine can decide to remove them when unnecessary, as in say e^(x+y).

>> So such issues lead towards to the design of a new language, rather than relying on an already existing.
> 
> and then the not foreseen limitations in that language and ugly extensions spoil it ... (btw, the nice thing about lua is that it's so stable)

One might focus on different parts communicating via the semantics of the underlying engine. Then with extensions, it is not necessary to know the syntax of other additions when writing the code. This is roughly how pure math works, and also the point extensible computer languages to get stuck on. And this is alos how Lua was added ro TeX.


___________________________________________________________________________________
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:[~2016-05-16  8:59 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-14 17:11 Hans Åberg
2016-05-15 13:37 ` Hans Hagen
2016-05-15 14:15   ` Hans Åberg
2016-05-15 14:28   ` Hans Åberg
2016-05-15 14:44     ` Wolfgang Schuster
2016-05-15 16:06       ` Hans Åberg
2016-05-15 16:36       ` Hans Åberg
2016-05-15 17:12         ` Hans Hagen
2016-05-15 17:28           ` Hans Åberg
2016-05-15 18:06             ` Hans Hagen
2016-05-15 18:34               ` Hans Åberg
2016-05-15 17:08     ` Hans Hagen
2016-05-15 17:42       ` Hans Åberg
2016-05-15 17:59         ` Hans Hagen
2016-05-15 18:31           ` Hans Åberg
2016-05-15 18:42             ` Hans Hagen
2016-05-15 20:06               ` Hans Åberg
2016-05-15 21:18                 ` Hans Hagen
2016-05-15 21:55                   ` Hans Åberg
     [not found]                     ` <f175caa5-45df-5df6-d5a9-5bf9340a6f0d@wxs.nl>
2016-05-16  8:27                       ` Hans Åberg
2016-05-16  8:48                         ` Hans Hagen
2016-05-16  8:59                           ` Hans Åberg [this message]
2016-05-16  9:10                             ` Hans Hagen
2016-05-16 12:07                               ` Hans Åberg
2016-06-16 19:15                 ` Hans Åberg
2016-06-16 21:48                   ` Hans Hagen
2016-06-16 23:02                     ` Hans Åberg
2016-06-17  4:20                       ` Alan BRASLAU
2016-06-17  8:15                         ` Hans Åberg

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=4365BE58-B85A-4B7F-81B8-C5AE92A28E6C@telia.com \
    --to=haberg-1@telia.com \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).