Changing from \def to \newcommand*

Question

Consider the following example:

\documentclass{article}

\usepackage{pstricks-add}
\def\door(#1,#2)#3{
  \psline[
    linecap = 0,
    linewidth = 1.5\pslinewidth,
    linecolor = white
  ](#1,#2)(!#1 #2 #3 add)
  \psline[
    linecap = 2
  ](#1,#2)(!#1 #3 add #2)
  \psarc[
    linestyle = dotted
  ](#1,#2){#3}{0}{90}
}

\begin{document}

\begin{pspicture}(1,1)
  \door(0,0){1}
\end{pspicture}

\end{document}

Is it possible to change \def to \newcommand* and keep the syntax

\door(a,b){c}

instead of

\door{0}{0}{1}

?

Be careful with unnecessary whitespaces in your macro body as \rput will not remove them. — kiss my armpit, Dec 12 '13 at 21:05
@DonutE.Knot Yes. This is one thing I have a problem with; to be honest, I have no idea when there will be whitespaces in my macros and when not. (I can of course end every line with % but this is a very tiresome task.) — Svend Tveskæg, Dec 12 '13 at 21:25
Missing out % at the end of a line does have a useful function of helping egreg keep ahead of us all as he earns most of his rep points by telling people to put % at ends of lines. — David Carlisle, Dec 12 '13 at 22:00
@lhf Because of What is the difference between \def and \newcommand?. — Svend Tveskæg, Dec 13 '13 at 01:41
But for your use, the pattern matching of \def seems ideal. — lhf, Dec 13 '13 at 02:02
\newcommand was intended to be less confusing than \def (DDP). Consequently, it is also less useful. — John Kormylo, Dec 13 '13 at 02:38

score 8 · Accepted Answer · answered Dec 13 '13 at 06:51

\def allows for specifying the parameter text that is to be expected, while \newcommand does not. xparse brings this back, but not with the simplicity that accompanies \def:

enter image description here

\documentclass{article}

\usepackage{pstricks-add,xparse}
\def\door(#1,#2)#3{
  \psline[
    linecap = 0,
    linewidth = 1.5\pslinewidth,
    linecolor = white
  ](#1,#2)(!#1 #2 #3 add)
  \psline[
    linecap = 2
  ](#1,#2)(!#1 #3 add #2)
  \psarc[
    linestyle = dotted
  ](#1,#2){#3}{0}{90}
}
\makeatletter
\NewDocumentCommand{\Xdoor}{ > { \SplitArgument {1} {,} } r() m}{% 
  \psline[
    linecap = 0,
    linewidth = 1.5\pslinewidth,
    linecolor = white
  ](\@firstoftwo#1,\@secondoftwo#1)(!\@firstoftwo#1 \@secondoftwo#1 #2 add)
  \psline[
    linecap = 2
  ](\@firstoftwo#1,\@secondoftwo#1)(!\@firstoftwo#1 #2 add \@secondoftwo#1)
  \psarc[
    linestyle = dotted
  ](\@firstoftwo#1,\@secondoftwo#1){#2}{0}{90}
}
\makeatother
\begin{document}

\begin{pspicture}(3,1)
  \door(0,0){1}
  \Xdoor(2,0){1}
\end{pspicture}

\end{document}

\SplitArgument{1}{,} splits r() - a required argument that is delimited by (...) - into two parts that should be separated by , in the following way: (a,b) > {a}{b}. As such, \@firstoftwo#1 results in a, and \@secondoftwo#1 results in b. Of course, you could define commands for these rather than \@first-/\@secondoftwo.

I'll just stick to \def but thanks for the nice answer. – Svend Tveskæg Dec 13 '13 at 10:25 — Svend Tveskæg, Dec 13 '13 at 10:25

Changing from \def to \newcommand*

1 Answers1

Linked