I get the same error if I try to enter a similar typeset piecewise in 2D Input mode using either the Expression palette or command-completion on the typed partial input piecewise . I see that whether I enclose the whole operator in delimiting brackets or if I explicitly type it as proc(t)... end proc.

So if that's what you were attempting then I'd say that yes, it's a bug.

acer

@Carl Love See here and here.

@sunflower Whether you want to type in the whole procedure line by line, or whether you want to paste it in, the important thing is that you don't input the Enter key alone, until you have input the end proc line.

Instead, after you have finished inputing each line, input the keystrokes Shift-Enter together, to move the input cursor down to the next line.

The Enter key will evaluate what you've typed so far in that section. The Shift-Enter combination will advance to the next line without evaluating. If you make Maple evaluate before you've completed inputing the whole procedure then you'll get an error message.

@Carl Love Yes, I meant Shift-Enter. Thanks Carl. I've corrected it.

@sunflower You need to put all the lines of code for the procedure into a single Execution Group or a single Paragraph.

By that I mean all the lines between and including the frame:= proc(n) and the end proc lines.

Do not hit the Enter (or Return) key between those lines of code. If you want to paste then in line by line then use the combined keystrokes Shift-Enter to advance to a new line. Or copy and paste the whole set of procedure lines at once.

If you mistakenly press the Enter key after only typing the frame:= proc(n) code then you'll get that error, because Maple will try to execute an incomplete procedure code body. It appears like you may be doing this.

@Lulu That example produces that error for me in Maple 2015.1 using 64bit Maple for Windows 7, with Digits set to 19 or higher (as far as can tell), but succeeds for Digits set to 18 down to 10 (all in fresh sessions).

I will submit a bug report.

@Lulu Digits is an enviroment variable that fsolve adjusts internally so as to increase the working precision in order to attain the desired accuracy.

Since it's an environment variable the changes made to Digits inside fsolve are not apparent when fsolve is left and control returns to the higher level.

Sometimes a badly conditioned example can foil fsolve's methodology. For example, `fsolve/polyill` can try repeated Digits-doubling in order to overcome numerical difficulties. But when that does not succeed then the maximal Digits value gets hit. It's also possible that some individual subcomputation which tries to determine by how much to increase Digits goes wrong and generates an invalid value (too high). These bugs are rare, but they can happen.

Having an example is useful, for debugging and for checking whether the problem persists in later versions.

@MDD Do you need to create them all up front, before you work on them? Do you care about memory allocation, or just about raw speed?

Do you really need them to be lists? Or would Vectors work?

If Vectors are ok, then would it be ok if you could create then in clumps (but not all at once), and then access them by indexing both by row and along a column?

The question about getting the most efficient way can depend on how you intend on using them.

Are you trying to say that you want to reflect the plot across the y-axis? eg,

P := plot( A, x0=-3..5 ):

plots:-display( P, plottools:-reflect(P, [[0,0],[0,1]]) );

acer

@Harry Garst 

Your second example of plot(0^(x^2), x=-3..3) may appear wholly flat because the point x=0 is not necessarily used as a data point by `plot`, and because your formula might run under evalhf mode.

But the following is somewhat related to my answer above, where the data points for x are explicitly specified. I used Maple 2015.1 below, but a similar effect was had in my Maple 18.02, both 64bit for Linux.

Download zeropow.mw

@Markiyan Hirnyk No, you are wrong. That was a problem with premature evaluation. This is different, being a distinction between behavior with exact exponent 0 and floating-point exponent 0.0.

@Markiyan Hirnyk 

Download goldy.mw

@Markiyan Hirnyk This is one of several times that you have failed by mistakenly pasting in 1D Maple Notation plaintext code in as 2D Input. That will not work in general. It is very bizarre that you keep making this mistake.

It doesn't matter that you try to convert to 1D input, after pasting in as 2D Input. It's the initial pasting in as 2D Input that is invalid.

Paste it in as 1D Maple Notation code, into an input prompt that is in 1D Maple Notation mode. That works.

@moeinvh What does the command

libname;

return in your fresh Maple session?

If it doesn't contain that new folder location then your initialization file is not being run. (Is it perhaps saved as maple.ini.txt by accident? Or saved as rich-text by accident? What editor did you use?)

It seemed to open Ok for me using 64bit Maple 2015.1 on Linux.

Attached is a zipped copy, with the sections expanded.

Tema_a1.zip

acer