ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: synonyms with MKIV
Date: Thu, 6 Dec 2007 09:45:18 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.0.9999.0712060939220.5906@nqv-yncgbc> (raw)
In-Reply-To: <4757C69F.9060902@wxs.nl>

On Thu, 6 Dec 2007, Hans Hagen wrote:

> Wolfgang Schuster wrote:
>
>> The order of key and entry is, the same as in the mkii macro
>>
>> { { v[2], v[3] } }, -- key, entry
>>
>> but you wrote
>>
>> { { v[3], v[2] } }, -- entry, key
>
> ok, fixed
>
> just wondering ... now we move to a mix of tex and lua code, how complex
> is it to piece together what's happening now inside context

I think that it is going to be easier (once you get the hang of it). When 
I started reading mkii code, I understood the steps that were being 
followed, but the fine details were pretty hard to understand. With 
luatex, the broad steps are still in tex, so that part is the same, but 
the fine implementation (that needed a real programming language) are in 
lua. This makes it much easier to understand. I could read the new mkiv 
pretty printing code and see what it was doing. With the mkii pretty 
printing  code, I spent about a week and was still clueless (rather, I 
understood bits and pieces, but there was no way I could extend it to 
another language).

I think that this is enough to overcome to compensate for the overhead 
between going back and forth between lua and tex code.

Aditya
___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


      reply	other threads:[~2007-12-06 14:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-03 16:44 Peter Münster
2007-12-03 17:58 ` Wolfgang Schuster
2007-12-03 19:18   ` Hans Hagen
2007-12-03 19:32   ` Hans Hagen
2007-12-04 15:57     ` Wolfgang Schuster
2007-12-04 18:22       ` Peter Münster
2007-12-05  8:29         ` Wolfgang Schuster
2007-12-05 20:45           ` Peter Münster
2007-12-05 22:06             ` Hans Hagen
2007-12-06  8:26               ` Wolfgang Schuster
2007-12-06  9:53                 ` Hans Hagen
2007-12-06 14:45                   ` Aditya Mahajan [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=alpine.DEB.0.9999.0712060939220.5906@nqv-yncgbc \
    --to=adityam@umich.edu \
    --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).