From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: the difference between \def and \define
Date: Tue, 16 Apr 2013 18:03:09 +0200 [thread overview]
Message-ID: <516D763D.3040705@wxs.nl> (raw)
In-Reply-To: <20130416101132.GI5709@homerow>
On 4/16/2013 12:11 PM, Marco Patzer wrote:
> On 2013–04–16 Thomas A. Schmitz wrote:
>
>> 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?
>
> Sorry, misunderstanding on my part. That one looks fine. I thought
> we're talking about translating the number to words, which wouldn't
> make any sense:
>
> \define[3]\foo{#one, #two, #three}
>
> I still don't think it's necessary to use named parameters with
> \define. For modules most likely \def, \setvalue or texdefinition
> are being used and \define for in-document markup, wherefore
> numbered parameters are perfectly fine. The only thing that could be
> improved is a definition which doesn't interfere with \asciimode,
> but that's low priority and can easily be worked around.
It's also messy (in parsing):
\define[#one,#two]\test{#one#two}
there we have to collect and move the test backwards. Also, names
defeats the use of the one number becoming multiple #'s so it then close to
\define\test[#one,#two]{#one#two}
which is nearly
\def\test[#one,#two]{#one#two}
apart from the checking, so i decided to provide this:
\checked\def \whatevera#alpha#beta{#alpha + #beta}
\checked\edef\whatevera#alpha#beta{#beta + #alpha}
\unique \def \whateverb#alpha#beta{#alpha + #beta}
\unique \edef\whateverb#alpha#beta{#beta + #alpha}
\whatevera{1}{2}\par
\whateverb{1}{2}\par
(can be used with \def \edef \xdef \gdef \udef \uedef \uxdef and \ugdef)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 16:03 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
2013-04-16 10:11 ` Marco Patzer
2013-04-16 16:03 ` Hans Hagen [this message]
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=516D763D.3040705@wxs.nl \
--to=pragma@wxs.nl \
--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).