@mmcdara Yes, they're quite different from each other.

That use of Typesetting:-Suppress affects how f(x) is pretty=printed in 2D Output in the Standard Java GUI (ie, typeset). But it doesn't relate to the plaintext input I type on my keyboard. It has the effect that the call f(x) is pretty-printed as just f, in 2D Output.

But alias(f=f(x)) does other things. For example,

restart;
alias(f=f(x));

                f

eval(f, x=3);

               f(3)

So that has changed what happens when I input the name f. And the way the call alias(f=f(x)) works can depend on some prior assignment.

@nm Having a shared engine (kernel) would be best illustrated by a value of some assigned name in one sheet affecting the same name in other sheet. The problem you describe with "restart" may (or may not) be due to the very same thing.

How is it functioning for you? Are you seeing the behaviour of distinct kernels (engines) across worksheets? Or are you seeing collision amongst assigned names and state, between worksheets?

@mnovaes The first argument passed to subs, ie. x=4 , is evaluated up front and becomes 3=4 even before the subs command receives it.

restart;

x := 3;

            3

trace(subs):

subs(x=4, 3);

 execute subs, args = 3 = 4, 3

            4

# Compare with, say,

subs('x'=4, 3);

 execute subs, args = x = 4, 3

            3

@mmcdara I suppose (hope?!) that this is all about interactive use, in which case alias is often useful and I don't object to it. If it works for you, then that's great.

I tend to look at things in a more programmatic perspective, in which I prefer not to assign to names which I still want to use as if they were unassigned. I suppose my preference is for approaches that work reasonably in both interactive and programmatic scenarios, where "reasonably" often has a connotation of scaling efficiently (as well as being straightforward to program).

@biol Do you mean something like this?

Or do you want to proceed the other way (formulaically), starting with an odd number and computing an even square that might be subtracted?

If it's homework/assignment/coursework, then how much of this do you think your ought to figure out yourself?

Download odd_stuff2.mw

@nm That last aspect you mention is due to typesetting=extended. That is a problem with the normal output, and unrelated to the userinfo messages.

On my Maple 2021.2 for Linux (by default, with no initialization) I get standard returned by interface(typesetting) and do not see that issue when redirecting the normal output to a text file. I understand that on Windows it is different.

So you try could including the command,

   interface(typesetting=standard):

You could even put that command right before your writeto call which redirects to a file. (Your could also put another call right after your latter writeto call, if you want to reinstate an earlier setting.)

If that still doesn't work the I'd be interested to know whether the following works (retaining every separate execution group verbatim):

Download userinfo_redef2.mw

@Johan159 This call is crazy:

assign(sol1);

@lcz Nice challenge. I've got the initial frame's rendering to respect the stylesheet option (passed through). Getting the updates (upon dragging) to respect that is a bit more challenging. Hopefully I'll find a little time on the weekend.

I could believe that having larger (padded) vertex labels might make it easier to "grab" them for dragging.

Maple 2021 --  March 10
Maple 2020 --  March 12
Maple 2019 --  March 14  (Pi day)
Maple 2018 --  March 21

@AHSAN Please put your close follow-up queries and details here, instead of spawning a separate Question thread.

Please put followup details for this query here, in Comments/Replies, instead of submitting a separate Question thread.

@John2020 Is this the kind of thing you're after? (If so then please test with nontrivial examples of your own. It's easy to overlook cases when coding.)

Download para_deg.mw

Here is a simple revision of that AltDGI procedure, which handles Matrices as well as lists (of Graphs).

graph_interactive_table_acM.mw

@nm Ok, so you only need assertion-checking for the local-variable and return-value type checks of your own procedures. That's more detail.

In that case either of the ways I showed of temporarily disabling certain kinds of assertion-checking in your calls to Library code might help with the kind of example you've shown.