From: Aditya Mahajan <adityam@umich.edu>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Info about creating modules for beginners.
Date: Sun, 26 Sep 2010 11:48:22 -0400 [thread overview]
Message-ID: <AB927FA5-E420-4205-9E14-0E2DE4AABDAB@umich.edu> (raw)
In-Reply-To: <4C9F2D7A.10801@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 974 bytes --]
On Sep 26, 2010, at 7:24 AM, Hans Hagen <pragma@wxs.nl> wrote:
> On 26-9-2010 2:02, Aditya Mahajan wrote:
>
>> Does it make sense to copy the definition of mult-aux.mkiv to mkii?
>> Everything other than \definenamespace should work in both mkii and
>> mkiv. That way, I can use it in modules that target both mkii and mkiv.
>
> if you consider it useful ... keep in mind that it uses the new inheritance model of mkiv (less predefined hash entries at the cost of a bit more runtime but also more powerful) ... adding it would not mean that I'd adapt all old mkii code to it
I understand. I am not asking any change in the mkii code. Just want the macros for the inheritance code (without the definenamespace macro that uses lua) to be available in mkii so that I can use the new inheritance model with mkii in my modules. (I use it anyways, but with boilerplate macros borrowed from Wolfgang. All I want to do is reduce that boilerplate)
Aditya
[-- Attachment #1.2: Type: text/html, Size: 1527 bytes --]
[-- Attachment #2: Type: text/plain, Size: 486 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-09-26 15:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 16:35 Jaroslav Hajtmar
2010-09-23 20:32 ` Hans Hagen
2010-09-23 20:42 ` Steffen Wolfrum
2010-09-23 20:47 ` Wolfgang Schuster
2010-09-23 21:08 ` Steffen Wolfrum
2010-09-23 21:15 ` Hans Hagen
2010-09-23 21:15 ` Wolfgang Schuster
2010-09-23 21:21 ` Aditya Mahajan
2010-09-23 21:38 ` Wolfgang Schuster
2010-09-23 21:42 ` Aditya Mahajan
2010-09-23 21:46 ` Wolfgang Schuster
2010-09-24 4:26 ` Aditya Mahajan
2010-09-24 7:04 ` Peter Münster
2010-09-23 21:30 ` Steffen Wolfrum
2010-09-23 21:36 ` Jaroslav Hajtmar
2010-09-23 21:43 ` Wolfgang Schuster
2010-09-25 15:07 ` \definenamespace and module setup (was: Info about creating modules for beginners.) Philipp Gesang
2010-09-25 17:35 ` Wolfgang Schuster
2010-09-27 8:30 ` Philipp Gesang
2010-09-23 22:08 ` Info about creating modules for beginners Steffen Wolfrum
2010-09-23 21:17 ` Aditya Mahajan
2010-09-23 21:21 ` Steffen Wolfrum
2010-09-23 20:46 ` Wolfgang Schuster
2010-09-26 0:02 ` Aditya Mahajan
2010-09-26 11:24 ` Hans Hagen
2010-09-26 15:48 ` Aditya Mahajan [this message]
2010-09-26 14:06 ` Wolfgang Schuster
2010-09-26 15:41 ` Aditya Mahajan
2010-09-26 17:51 ` Peter Münster
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=AB927FA5-E420-4205-9E14-0E2DE4AABDAB@umich.edu \
--to=adityam@umich.edu \
--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).