PyneComp v6.0.53 — converting older Pine scripts (v1–v5) is noticeably more reliable:…

Fixes

• A script that declares a type and a function under the same name no longer converts into code referring to a class that doesn’t exist.
• A user-type field whose default reads a built-in (close, time, …) now takes its value when the object is created, instead of being frozen at load time.
• A ?: with a numeric condition no longer breaks the line it sits on — function headers, if, while, else if, switch and for ... to heads all convert correctly now.
• Chained method calls such as array.get(holder, i).method() stay intact; previously conversion split them and the result failed with “Function … is not declared!”.
• Temporary variables the converter introduces no longer land in front of an else if or inside a switch branch, which used to produce “Unexpected start of an else-if line”.
• Pine v1/v2 declarations that take an if/for block result while the body reads their own history (alpha = if ... with alpha[1] inside) now convert into something that actually compiles.
• In Pine v4, a space between a call name and its arguments (barssince (x) and y) no longer strips the parentheses.
• Pine v4 scripts that bind an input type to a name (integer_ = input.integer) convert cleanly — v5 removed those constants, so the binding is dropped.
• x += switch ... is kept as written instead of being rewritten into a form Pine rejects.