@Markiyan Hirnyk The solution set over the complex numbers has one free parameter (to be expected since there are three unknowns and only two equations) whereas the solution set over the real numbers has zero free parameters.

@Markiyan Hirnyk That's because Alejandro's solution seemed to illustrate a general technique that could be applied to many problems. Indeed, solve(sys, vars, parametric, real) may be a complete replacement for the totally unreliable RealDomain:-solve when sys is polynomial.

Pagan's solution, on the other hand, seemed highly specialized because of the reason that I mentioned in my comment to that solution.

@Markiyan Hirnyk That's because Alejandro's solution seemed to illustrate a general technique that could be applied to many problems. Indeed, solve(sys, vars, parametric, real) may be a complete replacement for the totally unreliable RealDomain:-solve when sys is polynomial.

Pagan's solution, on the other hand, seemed highly specialized because of the reason that I mentioned in my comment to that solution.

@EWI If you remove the inequalities, solve will quickly return nine solution sets for the equations.

So, changing your colons to semicolons, we see that the solution set is a one-dimensional subset of C^3, but its intersection with R^3 is zero-dimensional.

So, changing your colons to semicolons, we see that the solution set is a one-dimensional subset of C^3, but its intersection with R^3 is zero-dimensional.

That's tricky as there are no parameters. I guess that the difference from regular solve is that it uses the SolveTools:-SemiAlgebraic algorithm, which in turn uses the massive RegularChains package.

It is also interesting that the solution is returned as a listlist.

That's tricky as there are no parameters. I guess that the difference from regular solve is that it uses the SolveTools:-SemiAlgebraic algorithm, which in turn uses the massive RegularChains package.

It is also interesting that the solution is returned as a listlist.

@GOODLUCK Why do your equations contain, repeatedly, expressions such as A/A, ctilde^s/ctilde^s?

@ysf Could you provide more details, please? Does it put the entire program in a single long line in the file? Could you upload your Maple code, please?

@ysf Could you provide more details, please? Does it put the entire program in a single long line in the file? Could you upload your Maple code, please?

@GOODLUCK What do you mean by calling mutilde^H, etc., "variables"? The variable is mutilde, and mutilde^H is an expression. It wouldn't matter if mutilde always appeared as mutilde^H, but it also appears as mutilde^B.

Because of your mixed used of capital letters, I can't tell whether you are using codegen[fortran] or CodeGeneration[Fortran]. So which one is it?

What version of Maple are you using? Your applyrule works for me in Maple 17. You need to correct the result to (X^(2*k) - Y^(2*k))^n. But even without the correction, the applyrule works.

@wolfman29 It is a bug, because it is supposed to accept functions that way in 2D input, with a popup asking whether you want to define a function or make a remember table entry.