ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Bruce Horrocks via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: How to extend an existing macro to take optional parameters?
Date: Mon, 13 Mar 2023 22:39:29 +0100	[thread overview]
Message-ID: <7b7e83ac-0e4b-ac37-c1c2-b0e715de837a@freedom.nl> (raw)
In-Reply-To: <FA67C545-4984-4545-B39F-AA931DEDD178@scorecrow.com>

On 3/12/2023 2:24 PM, Bruce Horrocks via ntg-context wrote:
> I have an existing macro that I'd like to extend.
> 
> The current definition is \define[3]\mycommand{...} which I'd like to extend to take an optional 4th parameter plus an optional setup parameter.
> 
> Thus I currently invoke it as:
> 
>    \mycommand{aa}{bb}{cc}
> 
> and I'd like to be able to extend it so that any of the following can be used:
> 
>    \mycommand{aa}{bb}{cc}
>    \mycommand{aa}{bb}{cc}{dd}
>    \mycommand{aa}{bb}{cc}{dd}[ee]
> 
> or
> 
>    \mycommand[ee]{aa}{bb}{cc}{dd}  % if this is more the ConTeXt way
> 
> where {dd} is the optional extra parameter and, if it is present, then [ee] can also be optionally added (because it controls how {dd} is printed).
> 
> If it helps, the actual body of the macro can easily be a call to Lua so it's fine if the function takes 5 params where 4 and 5 can be nil or empty strings.
> 
> I've trawled through syst-aux.mkiv but it only covers optional numbers of [ ] or { } but not combinations of both (which given the vast numbers of combinations is perhaps not surprising!). Have I missed something obvious that would help me?
So, four optional with mandate {} plus a fallback to an optional []

\starttext

\tolerant\def\mycommand#=#=#=#=#:[#5]%
   {\ifparameter#1\or(1:#1)\fi
    \ifparameter#2\or(2:#2)\fi
    \ifparameter#3\or(3:#3)\fi
    \ifparameter#4\or(4:#4)\fi
    \ifparameter#5\or[5:#5]\fi}

\startbuffer
\mycommand{aa}{bb}{cc}
   \mycommand{aa}{bb}{cc}{dd}
   \mycommand{aa}{bb}{cc}{dd}[ee]
\mycommand{aa}{bb}{cc}
   \mycommand{aa}{bb}{cc}{dd}
   \mycommand{aa}{bb}{cc}{dd}[ee]
\stopbuffer

\typebuffer

\startlines \getbuffer \stoplines

\stoptext

I'm not saying that it's the best solution, you can add \protected in 
front of the \def if needed.

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | 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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2023-03-13 21:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-12 13:24 Bruce Horrocks via ntg-context
2023-03-13 21:39 ` Hans Hagen via ntg-context [this message]
2023-03-14  2:08   ` Alan Braslau via ntg-context
2023-03-15  1:32     ` Bruce Horrocks via ntg-context
2023-03-15  1:27   ` Bruce Horrocks via ntg-context

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=7b7e83ac-0e4b-ac37-c1c2-b0e715de837a@freedom.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@freedom.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).