From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: the difference between \def and \define
Date: Tue, 16 Apr 2013 11:10:30 +0200 [thread overview]
Message-ID: <516D1586.5070705@uni-bonn.de> (raw)
In-Reply-To: <20130416090552.GH5709@homerow>
On 04/16/2013 11:05 AM, Marco Patzer wrote:
> It doesn't make sense to use named parameters with
> \define, since you explicitly pass the parameter*number* in
> brackets. You cannot refer to a number by name. Well, you could
> theoretically, but I'd strongly object.
Just out of curiosity: why would you object? In Lua, we have the syntax
function whatever(one, two, three)
do something with(one, two, three)
end
I'm not lobbying for define to have something similar, I just want to
point out that it would be in the spirit of convergence between ConTeXt
and Lua. It certainly isn't an urgent need, but having
\define[one,two,three]
wouldn't be absurd, now would it?
Thomas
___________________________________________________________________________________
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:[~2013-04-16 9:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 13:47 Tim Li
2013-04-15 14:04 ` Wolfgang Schuster
2013-04-15 14:07 ` Marco Patzer
2013-04-15 14:12 ` Hans Hagen
2013-04-15 14:21 ` Wolfgang Schuster
2013-04-16 8:42 ` Hans Hagen
2013-04-16 9:05 ` Marco Patzer
2013-04-16 9:10 ` Thomas A. Schmitz [this message]
2013-04-16 10:11 ` Marco Patzer
2013-04-16 16:03 ` Hans Hagen
2013-04-16 10:34 ` Hans Hagen
2013-04-16 11:14 ` Alan BRASLAU
2013-04-16 12:01 ` Hans Hagen
2013-04-15 14:26 ` Marco Patzer
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=516D1586.5070705@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).