On 8/7/16, 2:04 PM, "Harbs" <harbs.li...@gmail.com> wrote:
>Yes. That would be better (only 1.5KB), but only in this case. Assigning >a null value to a string should not covert it into an empty string. > >I was suggesting to have an option to not do any conversions. > >Right now my code works without any string conversion at all. This is >because of the “string-like” functions I added to XML and XMLList, as >well as explicit conversions in the beginning of my function calls: I looked at your changes. That's a clever idea. It would probably fail the typeof test. We could hack is/as to accept it as well if we want. We could add options to suppress conversions. I'd be tempted to do it at the class or method level instead of as a configuration option that would affect all files. We have "directives" like @flexjsignorecoercion that we are already using to alter output. Thoughts? -Alex
