Problem $2$: Parameter Passing II

Like Call by Name parameter$-$passing mechanism, Call by Macro Expansion technique also uses a lazy evaluation technique. It is widely used in C$,$ C$++,$ etc. Unlike function calls, macros do not have runtime overhead because they are expanded at compile$-$time $($before actual code execution$).$ Macro expansion works in the following way:

No evaluation: The literal text of each macro argument is substituted for the corresponding parameter in the macro's body.

No evaluation: The resulting macro body is then textually inserted into the program where the macro was called.

Evaluation: The expanded macro code is executed in the caller's environment, meaning the variables and expressions are evaluated as if they were part of the original calling code.

Below are two functions that implement the Call by Macro scheme. Each function accepts a single parameter $x,$ which can either be a numerical value $(-1,2,0,$ etc.$)$ or an arithmetic expression consisting of numbers, and the arithmetic operators from set $.$For each function, indicate whether there will be any issues when using the Call by Macro parameter$-$passing scheme. If issues exist, explain why they occur and suggest how to fix them. Otherwise, explain why there is no issue.

Note $1$: You should not consider changing the parameter$-$passing scheme as a potential fix.

Note $2$: Check related exercises from this link to learn more about macro expansion $($collected from the optional reading material section of Module Week $6).$