So, I will try it (even though I find Emacs' design barely tolerable). How do you configure it to use different versions of Maple? May be that you add some notes to your blog post?

By the way, I cannot distinguish any Maple code against the black backgound of those screenshots.

It seems that for now the easier workaround is going back to the 2D ascii interface(prettyprint=1) output:

    4              1
y(x)  = -----------------------
        1/4 - x + exp(-4 x) _C1

It seems that for now the easier workaround is going back to the 2D ascii interface(prettyprint=1) output:

    4              1
y(x)  = -----------------------
        1/4 - x + exp(-4 x) _C1

Most probably the interesting physical situation corresponds to different diffusion constants  in the film and in the substrate. Hence, a boundary condition at the interface is needed to match the solutions of the two regions.

Most probably the interesting physical situation corresponds to different diffusion constants  in the film and in the substrate. Hence, a boundary condition at the interface is needed to match the solutions of the two regions.

you will realize that the subject of this thread is not procedures with parameters of type set or procedures in general. So, nobody has written here about an algorithm that will determine the domain of a general proc.

you will realize that the subject of this thread is not procedures with parameters of type set or procedures in general. So, nobody has written here about an algorithm that will determine the domain of a general proc.

whattype(Wisconsin);
                                symbol

Then Wisconsin is a name as any other name. For some parameters in a subset of commands in Maple, names are taken to represent complex variables. For them, Wisconsin may represent a point on the complex plane.

Within the context of this thread, domain means a subset of the real axis or the complex plane. In this context, you may use 'Wisconsin' instead of 'x' or 'z'.

whattype(Wisconsin);
                                symbol

Then Wisconsin is a name as any other name. For some parameters in a subset of commands in Maple, names are taken to represent complex variables. For them, Wisconsin may represent a point on the complex plane.

Within the context of this thread, domain means a subset of the real axis or the complex plane. In this context, you may use 'Wisconsin' instead of 'x' or 'z'.

I think that it is mostly oriented to interactive usage, as an online handbook of functions with output that can be used for computations (eg use of identities in substitutions). I wonder whether the information stored there is used somewhere else in the code. And I have not found an interlink in the pages of the "Mathematics and Engineering Dictionary" that refer to the same functions, so that some information is, in a sense, duplicated.

Perhaps that information could be used, in some cases,  for  an algorithmic  determination of the domain  of a function (instead of  starting from "first principles", ie the definition of the function).

I think that it is mostly oriented to interactive usage, as an online handbook of functions with output that can be used for computations (eg use of identities in substitutions). I wonder whether the information stored there is used somewhere else in the code. And I have not found an interlink in the pages of the "Mathematics and Engineering Dictionary" that refer to the same functions, so that some information is, in a sense, duplicated.

Perhaps that information could be used, in some cases,  for  an algorithmic  determination of the domain  of a function (instead of  starting from "first principles", ie the definition of the function).

The packages 'SumTools' and 'sumtools' are devoted to "computation", while 'IntegrationTools' has commands only for manipulation. Perhaps it should be another package, named 'SumationTools' say, just for manipulation.

The packages 'SumTools' and 'sumtools' are devoted to "computation", while 'IntegrationTools' has commands only for manipulation. Perhaps it should be another package, named 'SumationTools' say, just for manipulation.

What does it mean "up to deciding zero of the underlying domain"?

"Certain classes of functions" mean something like elementary functions?

Sounds to me as if too much nesting produces a complexity limit when only elementary like functions are involved. For special functions, even shallow, some other issues should also generate complications.

What does it mean "up to deciding zero of the underlying domain"?

"Certain classes of functions" mean something like elementary functions?

Sounds to me as if too much nesting produces a complexity limit when only elementary like functions are involved. For special functions, even shallow, some other issues should also generate complications.