ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Zhichu Chen <chenzhichu@sinap.ac.cn>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: conTeXt Mkiv: the number of parameters can not be more than 9?
Date: Sun, 5 Jul 2015 11:40:47 +0800	[thread overview]
Message-ID: <5598A73F.2030504@sinap.ac.cn> (raw)
In-Reply-To: <CADT5_18RUYos72e+jv=MXPtH8Bnhb76ih6q5hmaiouV3BekHsA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2099 bytes --]

Hi Dillon,

First of all, I'm against defining such a complex macro, since that can 
be very
confusing when you use it. I personal prefer the key-value definition:
\def\DEFINETEST[#1]{%
   \getXXXparameters
     [paraA=defaultValueForParameterA%
     ,paraB=% or just empty
     ,#1]%
   \doSomethingWith[\XXXparameter\paraA]%
   \doSomethingElse...
}
You might want to refer to the following link and other valuable 
materials on the
wiki for more information:
http://wiki.contextgarden.net/System_Macros/Key_Value_Assignments

If you insist on that, I guess you can define a temporary macro inside 
your macro.
That's very dirty, but can be a little more efficient? I'm not sure.

I was given to understand that the ConTeXt MKVI now accepts parameters 
such as
#position#color rather than meaningless #1#2. I GUESS that's lua-based, 
so maybe
it'll break the TeX limitation.

On 07/05/2015 09:55 AM, 土卜皿 wrote:
>
> hi, all
>
> For testing, I have a definition:
>
> |\define[9]\DEFINETEST{#1,#2,#3,#4,#5,#6,#7,#8,#9}|
>
> |context test| can work fine, when I modify the above into:
>
> |\define[10]\DEFINETEST{#1,#2,#3,#4,#5,#6,#7,#8,#9,#10}|
>
> I got a error:
>
> |test.tex: ! Illegal parameter number in definition of\DEFINETEST|
>
> From StackExchange, I got a answer:
>
> Since ConTeXt is based on TeX, the maximum number of 9 parameters is 
> inherited
>
> So, in Context mkiv, what should I do for more than 9 parameters?
>
> Thanks!
>
> Best Regards
>
> Dillon
>
>
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________


-- 
Best regards,
ℤh𝕚chu ℂh𝕖n


[-- Attachment #1.2: Type: text/html, Size: 9968 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
___________________________________________________________________________________

  reply	other threads:[~2015-07-05  3:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-05  1:55 土卜皿
2015-07-05  3:40 ` Zhichu Chen [this message]
2015-07-05  4:06   ` 土卜皿
2015-07-05  4:36 ` Jaroslav Hajtmar

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=5598A73F.2030504@sinap.ac.cn \
    --to=chenzhichu@sinap.ac.cn \
    --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).