PyneComp v6.0.57 — Pine v5 scripts that previously failed to convert with a confusing…

Fixes

• Converting a script where an if, while or else if condition was followed by a comment on the same line produced a broken script — everything after that line collapsed into it. The error pointed at a line you never wrote.
• Conditions written without a space around and/or, such as (a > b)and c, were mangled into a single invalid name and rejected.
• A multi-line call whose first line ended in a comment — for example table.new(pos, 2, 7, // rows — was left broken, and conversion failed on one of the argument names.
• A for header split across lines could get its by 1 inserted into the middle of an expression, producing a script that would not compile.
• Parentheses and text inside string literals were being rewritten, silently changing what your strings contained.
• Escape sequences such as \t and \n lost their backslash, changing a string’s actual value; \' could produce a script that failed to compile.
• Comments could disappear from converted scripts when a statement was folded onto one line. They are now kept, except in the TradingView-identical conversion mode, which reproduces TradingView’s own behaviour exactly.