• is the evaluation of piecewise exited, if the first condition is satisfied
• or does it run through all the conditions?

(sorry, do not have Maple installed here ...)

1. Do not know ... may be your cursor was placed on some output
in that case I would go to the 1st input line of the sheet

2. The editor is somewhat weak ... usually I do such things through
a text editor (replace newLine + > + blank by newLine)

3. Maple has at least 2 possibilities for output and what you observe
is working like a print command - this is intended and ok

1. Do not know ... may be your cursor was placed on some output
in that case I would go to the 1st input line of the sheet

2. The editor is somewhat weak ... usually I do such things through
a text editor (replace newLine + > + blank by newLine)

3. Maple has at least 2 possibilities for output and what you observe
is working like a print command - this is intended and ok

Thx for the replies, I will try to restrict to cases, where the function is analytic

Alec, Alejandro ... :-(

Anyway, I have no reason to doubt for my 2nd statement/impression/hope ...

Alec, Alejandro ... :-(

Anyway, I have no reason to doubt for my 2nd statement/impression/hope ...

Alec,

there may be other reasons for the guys: rules, they have to obey.

And reading between some of Jacques' posts makes me guessing
that a good bunch of developers would prefer to improve things, but
are constrained to other tasks.

Concerning handling and comfort I agree with you (personally I do
prefer a clean interface without much gimmicks, but an editor with
common features should be included - even for the real interface
[i.e. the 'Classic' one])

Alec,

there may be other reasons for the guys: rules, they have to obey.

And reading between some of Jacques' posts makes me guessing
that a good bunch of developers would prefer to improve things, but
are constrained to other tasks.

Concerning handling and comfort I agree with you (personally I do
prefer a clean interface without much gimmicks, but an editor with
common features should be included - even for the real interface
[i.e. the 'Classic' one])

Sorry for the sloppy typo, should not have edited, so again (using Maple 12):

  f := x -> arctan(x^(1-I))+arctan(x^(-1+I));

  #f(x); plot([Re(%),Im(%)],x=0..0.3, color=[red,blue]);

  dd := PDEtools[dpolyform]( y(x) = f(x) , no_Fn);

                           d
                    dd := [-- y(x) = 0] &where []
                           dx

And the question remains: how to deal such piecewise functions
using dpolyform?

seems one needs to have f to be continous for using it on Int( f(x), x = 0 .. K ), otherwise odd behaviour can occure,
I have a related question here www.mapleprimes.com/blog/axelvogt/problemhandlingpdetoolsdpolyformanddsolve

Congratulations Mario, fine to hear that!

... beauty is in the eye of the beholder and Maple is not a type setting tool ... I already commented on that ... and mentioned a mathematical standard for notation in those case, take it or leave it - type in Standard sheet and copy paste in text region:

(-b +sigma*sqrt(b^2-4*c))/2, sigma in {+1,-1};

I would not use it - for the reason I already said.

Just type your formulae like " y = f(x) + s*g(x), s in {+1,-1} " which is a common way,
i.e. a factor taking the desired values.

I will never eally understand, why one expects a CAS to be a typesetting system as well ...

The following may cover your needs

  `+/-`;

  s in {`+`,`-`};

In this special case one can use a method which is part of 'identify':

  Digits:=20:
  k/Pi^4; subs(k=104,%); a:=evalf(%);

  w := [a, Pi, Pi^2, Pi^3, Pi^4, 1/Pi, 1/(Pi^2), 1/(Pi^3), 1/(Pi^4)]

  u:=IntegerRelations:-LinearDependency(evalf(w), method=LLL);

  'A'*u[1]+'Sum( u[i]*w[i],i=2..nops(w))': value(%); 
  eval( isolate(%,A), A=a);

  `error` = evalf(lhs(%)-rhs(%));


                                             104
                     1.0676621544871708597 = ---
                                               4
                                             Pi

                              error = 0.

This is very fast (but weaker than 'identify', it fails with 1/a).

Playing with it (higher precision, larger base) gives examples,
where it will be difficult to find a 'correct' presentation, the
precision may be up to the last decimals - but are not correct
(mainly because of rational representations of floats).