And I can sense the threshold transition. But I can not stop the deeper and deeper recursions unless I hack the manipulation that I expect the lexer or filter that supplies me with SYMT derived type specificity for tokens manifesting in this parse. There is a need to halt the recurse, to prevent malicious code from being at compiler crash. Some of that commentary is also meant to clarify for one who was kind enough to respond to some of my earlier posts. I do not say we need 50 explicitly distinct rules to deal with OFIN agglutinations.
Any recursive tool works fine.
However, I do remain convinced that it would be good to distinguish reference modifiable, subscriptable, and function references by type in distinct tokens. And the discussion of valid depth should not be taken as an agreement about best maximum depth actually coded. I have that idea of an error manager as the primary design concept for the compiler.