@Joe Riel I can't reproduce it either anymore. But I reproduced it about a dozen times before posting.

However, there's still the issue of the args being reported as a large integer by trace. That's not a big concern, but I wonder if it's happening for you.

I just finished the code and posted it to the "Bifurcation in Maple" thread with some very interesting plots.

@Joe Riel There are often requests here for some way to circumvent automatic simplification for display purposes. Your 3/3 shows that you have done this. I've also checked that it is possible to make the denominator 0. These forms seem to be stable. I got 3/3 + 3 = 12/3, and 1/0 + 1 = 1/0.

I have often wished that evalindets had an option recurse which would cause it to use eval[recurse] instead of regular eval.

How do you use ifelse? I can find no documentation, nor does eval(ifelse) return anything useful.

@Les When you're entering or editing the Question, there's a pull-down menu that lists Maple, MapleSim, MapleTA, MaplePrimes, etc.---the various Maplesoft products that are discussed on this forum. While the vast majority of the discussion here is about Maple itself, there are occasionally Questions about the others.

@Les The single quotes are used to guard against the possibility that elsewhere in your code you assigned a value to color, linestyle, spacedash, etc. If you've not assigned values to any of those, then the quotes make no difference. If you want to get even more fussy about it, you can make them, for example, ':-color', which would also guard against the possibility that the code is embedded in other code where color is used as a local variable.

To deal with indexed names and functions in the most general way, I think that it's necessary to localize the names (symbols) before they are assigned values. Like this:

RootSymbol:= (e::{symbol, indexed, function})-> `if`(e::symbol, e, thisproc(op(0,e))):
     
Localize:= proc(e)
local S:= RootSymbol~(indets(e, {symbol, indexed, function}));
     subs(S =~ convert~(S, `local`), e)
end proc:

Define your list or vector of column headers/entries:
Exprs:= [a, b(23)[34], c[b[a]^2+1]];

Headers:= Localize(Exprs):
a:= 1:  b:= B:  c:= f:
Matrix([Headers, Exprs]);

Now you can change the values of a, b, c at will, and the Headers will never change.

@rostam And do you have the same anti-aliasing setting on your laptop and PC? Use the menu Tools -> Options -> Display -> Plot anti-aliasing.

@Thomas Dean There's some (inadequte) discussion of using infix operators in prefix form at ?use. The operators that can be used in prefix form are `..`, `@`, `@@`, `.`, `+`, `*`, `-`, `/`, `mod`, `^`, `!`, `union`, `minus`, `intersect`, `subset`, `in`, `$`, `and`, `or`, `not`, `xor`, `implies`, `=`, `<>`, `<`, `<=`, `>`, `>=`, `assuming`, `<|>`, `<,>`, `[]`, `{}`, `?()`, `?[]`, and `~`. The sematics of and, or, and implies are slightly different in prefix form: They don't obey the McCarthy rules (perhaps this has been corrected in Maple 2016.1a; I haven't had a chance to check yet).

@Thomas Dean Please look closely to see the difference with and without the leading `=`. It's the same as the difference between a,b and a=b.

Also, pay heed to Kitonum's correction of my unfortunate mistake. I neglected the minus sign that comes from moving from one side of the equation to the other.

@Thomas Dean That's completely separate from this Question. Please ask it as a new Question, not as an irrelevant Reply to another Question. A Reply is meant to be a response to the material that precedes it.

@roman_pearce How'd you get Maple to say that the system is inconsistent? And if it is, why did I get a result from the command in my Answer (using Maple 16)? Are you sure that you used the correct variable names? It was a little tricky for me to get them right.

Axel and Acer, please see my Answer in the original thread, where I use the `property/object` table to get the intersection of intervals.

@sand15 That was my Answer. I deleted it because on a subsequent reading I decided that it didn't properly address the Question. That's because it only determined whether the intervals have nonempty intersection rather than finding what the intersection was.

I'll put the Answer back on the other Question. Sorry for the confusion.

Please post your worksheet as an attached file. The parts of your post that aren't plaintext can't be copy-and-pasted.

Also, distance and distancevector are used in your code and are never defined.