Expression Too Complex - some details?

If possible, I'd like to know exactly how MMF decides an expression is too complex.

I've got a few things worked out. Someone please correct me if these are wrong:

Strings
Each string in an expression must have 256 characters or less, not including the delimiting " characters.

This can be resolved by splitting a long string up, like this:

"String A" + "String B"

In this case, both strings A and B can have up to 256 characters, making the a total string of 512. This works from within the same expression.

Integers
There appears to be a maximum of 61 integers per expression, assuming no brackets. So if you do 1+1+1+1...+1+1, you can have a total of 61 '1's.

A set of brackets will take the place of 1 integer


But it doesn't always seem to fit, so if someone could explain a few more of the rules about long expressions, that'd be dandy :)

I believe there is a character limit but Francois would know for sure as this is his area.

very, interesting... and weird.

Yes there is a buffer limit (the compiled expression buffer). Can you post your expression? I am surprised that this limit can be reached...

I reach it often at the moment, everytime when i try to soften something by the surrounding knots. 9 Values to calculate. And have posted one example expression before:

http://reinerstileset.4players.de/ex...oocomplex2.jpg

I frequently get this problem as well... normally when executing an SQL statement

I get this problem very often with SQL queries too. Maybe having many double and single quotes mixed lead to a problem ?

It's a very common problem in complex expressions. I use immediate if statements a lot because they help work around object selection problems without fastloops, and this error can be very common once you have nested ifs.

Another thing you can do is use a nested min() function to retrieve the lower of five or six variables. If each variable is derived in a complex way, it can easily get too much. You end up having to create a bunch of alterable values to handle it.

But that said, it can still take a long expression. This is valid:

Quote:

---

min((CompareIntegers("Immediate If Object",find(edittext$("Edit Box"),"+",pointer("VARS")),">",-1,find(edittext$("Edit Box"),"+",pointer("VARS")),len(edittext$("Edit Box")))),min((CompareIntegers("Immediate If Object",(find(edittext$("Edit Box"),"-",pointer("VARS"))),">",-1,(find(edittext$("Edit Box"),"-",pointer("VARS"))),len(edittext$("Edit Box")))),min((CompareIntegers("Immediate If Object",(find(edittext$("Edit Box"),"/",pointer("VARS"))),">",-1,(find(edittext$("Edit Box"),"/",pointer("VARS"))),len(edittext$("Edit Box")))),(CompareIntegers("Immediate If Object",(find(edittext$("Edit Box"),"*",pointer("VARS"))),">",-1,(find(edittext$("Edit Box"),"*",pointer("VARS"))),len(edittext$("Edit Box")))))))

---

That finds the location of +, -, * or /, whichever comes first in a string.

Btw, that was generated by Expression Editor Plus, which is designed to help you code complex expressions. I want to know how MMF picks up errors so I can warn about them before exporting the expression.

EG. If an expression it generates will result in an 'Expression too Complex' error, I'd like to be able to process the string and find out why, and maybe make some suggestions on reducing it. Like "You've used a long string - try containing this in a string object and refering to it like in the following example:..." or "Your expression is simply too complex. MMF has a buffer limit. Would you like to use a wizard to split your expression in two?"

...that kinda thing.

sorry to revive a crazy old post... But I still get this all the time. There are ways around it.. but it would certainly be more convenient and make for less-chunky code if this limit can somehow be lifted.

not a huge deal.. just something that would be nice if possible. :)

What's wrong with dumping certain expressions to global strings and then parsing them with the expression editor to save on lengths?!

Dines, while we've caught you here would you mind reuploading EE+ somewhere? The link on TDC has been dead for ages.

EDIT: It'd be awesome if the expression limits were removed. Then I could release my two action platform engine (Always Set Y Position and Set X Position)

EDIT2: Also, if I recall correctly there are two expression limits, one for complexity and one for length. The length limit is as Dines said, but complexity is based on number of operations and cannot be solved by splitting it into two parts.

I always get hit with the expression length limit - especially when I'm working with strings, trying to join them together and whatnot. I often have to use the method mentioned previously of using one expression to combine a bunch of strings saved to values together.

I never have this problem, but it's because I avoid super long expressions just for the sake of clarity. Even if longer expressions are supported, you should still consider building those long strings in multiple actions just to make the events more understandable.

Util expressions can be formatted more visually pleasing (with line breaks and indenting among other things), just use an auxiliary global string that you dedicate for temporary uses.