Did you attempt to attach a model to that post?  I don't see it.

@alex_01 Those are warnings, not errors.  They can be ignored.  You can even turn them off by doing

interface(warnlevel = 1);

I prefer to declare the variables.

How much of this is OS dependent?  On my i5, 1.2GHz 64 bit linux box, your first test runs in approximatly 300 msec.  On my 64-bit Windows 7 laptop, with a 2GHz i7, it takes 3 seconds. That's a huge difference.

@Alejandro Jakubi That isn't what I meant, but I see what you mean, there is a bug such that when the slider is activated, the window goes blank.  I'll submit an SCR.

@Alejandro Jakubi That isn't what I meant, but I see what you mean, there is a bug such that when the slider is activated, the window goes blank.  I'll submit an SCR.

@Christopher2222 A list can be of (practically) unlimited size.  The limit of 100 applies to the operation of assigning to elements of a list.  For example

(**) L := [seq(1..100)]:
(**) L[1] := 2;
                                   L[1] := 2

(**) L := [seq(1..101)]: 
(**) L[1] := 2;         
Error, assigning to a long list, please use Arrays

@Christopher2222 A list can be of (practically) unlimited size.  The limit of 100 applies to the operation of assigning to elements of a list.  For example

(**) L := [seq(1..100)]:
(**) L[1] := 2;
                                   L[1] := 2

(**) L := [seq(1..101)]: 
(**) L[1] := 2;         
Error, assigning to a long list, please use Arrays

@Axel Vogt Yes, a Vector does not have that limitation. 

@Axel Vogt Yes, a Vector does not have that limitation. 

Doing

  c := copy(test)

and then later assigning to elements of c is not the best suggestion.  That limits the maximum list size to 100 elements since otherwise Maple will complain.  The reason for the arbitrary limit is to discourage that usage; it is inefficient because each assignment generates an entirely new list.

Doing

  c := copy(test)

and then later assigning to elements of c is not the best suggestion.  That limits the maximum list size to 100 elements since otherwise Maple will complain.  The reason for the arbitrary limit is to discourage that usage; it is inefficient because each assignment generates an entirely new list.

That only works if f permits a symbolic x parameter. Consider

 f := proc(k,x) if x < 1 then k else -k end if end proc:
plot([seq(f(k,x),k=[1,2,3])], x=0..3);
Error, (in f) cannot determine if this expression is true or false: x < 1

You can delay the evaluation of f by using forward quotes:

plot([seq('f'(k,x),k=[1,2,3])], x=0..3);

That only works if f permits a symbolic x parameter. Consider

 f := proc(k,x) if x < 1 then k else -k end if end proc:
plot([seq(f(k,x),k=[1,2,3])], x=0..3);
Error, (in f) cannot determine if this expression is true or false: x < 1

You can delay the evaluation of f by using forward quotes:

plot([seq('f'(k,x),k=[1,2,3])], x=0..3);

An amusing idea.

For whatever reason, I have the hardest time finding that keyword.  I know it is in kernelopts, but it never jumps out when scanning the list in the help page. Probably I'm looking for something with gc in it.  Some day I'll create a help page with two listings, one alphabetical and one functional, however, given the variety of stuff in there there may be no nice organization.