From: Marco Patzer <homerow@lavabit.com>
To: ntg-context@ntg.nl
Subject: Re: the difference between \def and \define
Date: Tue, 16 Apr 2013 11:05:52 +0200 [thread overview]
Message-ID: <20130416090552.GH5709@homerow> (raw)
In-Reply-To: <516D0EE6.2040004@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 620 bytes --]
On 2013–04–16 Hans Hagen wrote:
> >Marco tries to do something like
> >
> > \define[3]\Test{#one#two#three}
> >
> >which doesn’t work.
>
> hm, ok, do \define is not mkvi then ... too messy to catch that one too
No need to bother with that. I was just pointing out the differences
between \def and \define for Tim. And named parameters is something
\define can't do. 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.
Marco
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 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:[~2013-04-16 9:05 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 [this message]
2013-04-16 9:10 ` Thomas A. Schmitz
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=20130416090552.GH5709@homerow \
--to=homerow@lavabit.com \
--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).