Today I saw the following error:
U00003720 Error in Object 'UC4.SCM.V140.TRANSFER_NEW.JOBP' detected: A variable object is interlaced too much.
What does this error mean?
"in order to understand recursion you must first understand recursion".
I suppose they may have decided to not use the word recursion because it would imply an object was calling itself when this might not always be the case. I suspect they are trapping any situation where "too many" levels of execution are taking place no matter how it occurred.
I've got several implementations in this product where I cloned an object into "A" and "B" versions which can call one-another to bypass a rule that won't let certain types of objects call themselves. Rules like these are a double edged sword... great for stopping us from running accidental infinite loops, but they just get in the way of true recursive solutions.
Others have reported interlace errors as well. See this thread; What does Interlaced too much mean?
I think it means that there are too many levels of recursion, or that variable resolution cannot be performed because dependent variables haven’t been resolved. This is a VARA with several nested levels of VARA references.
The wording of the message is a bit odd. Aside from the context of interlacing of adjacent video frames, I have never seen the word ‘interlacing’ used in computer or software documentation before.
“Too many levels of variable reference” might be a better way to phrase it — assuming that is the actual problem of course.
I suppose they may have decided to not use the word recursion
I'm going to go with classical Okham's razor on this one: If you hear the sound of hooves, think horses, not zebras.
Reportedly Automic has non-native English speakers write English texts, then has an American company translate that back to e.g. German. I've seen too many "false friends" and some truly facepalm-worthy results come out of this process for my first impression to be "they chose that term because (reasons)". This may be the case sometimes, but my first impulse nowadays is to conclude "they chose that term because it's the first that came to mind".
Yeah, it’s clear that native English speakers were involved late in the process when they were involved at all.
I started a new discussion where we can document all of these errors in one place:
Inapt English language usage in AWA messages & documentation
I also posted a comment to this old idea, asking for CA to reconsider it in light of the recent CA-Automic union:
Clear, consistent, unambiguous terminology in products and documentation
Sorry, but this for once is one battle I will try to force myself not to participate in (I hope I can stick to that ), because there's just too much. I believe they need to find (a team of) proper English speakers who also have at least basic contextual knowledge of AE, and those English speakers need to overhaul all of their documentation (and a good part of other output, too) - if they want to appear truly professional in that aspect, in an international environment.
I've filed a few individual tickets for the worst "false friend" documentation errors in German and they got corrected, but as for all errors, not just the most egregious bits, I think that's just too many.
(edit: I will admit that the English AE manual isn't that bad, but the state of other materials, and of the German one probably also influence my perception to some extend ...)
Retrieving data ...