[GitHub] [royale-compiler] Harbs commented on issue #203: XML.toXMLString() not recognized by the compiler

2021-12-16 Thread GitBox
Harbs commented on issue #203: URL: https://github.com/apache/royale-compiler/issues/203#issuecomment-995757262 What defines XML as "dynamic"? FWIW, `xml[i]` (or `xmlList[i]`) can always be assumed to be XML. -- This is an automated message from the Apache Git Service. To respond

[GitHub] [royale-compiler] Harbs commented on issue #203: XML.toXMLString() not recognized by the compiler

2021-12-16 Thread GitBox
Harbs commented on issue #203: URL: https://github.com/apache/royale-compiler/issues/203#issuecomment-995747095 Much improved, but I found another case where it's not being resolved: ``` if(objXMLList.length() == 1){// no contents. Keep the background as a top level object

[GitHub] [royale-compiler] Harbs commented on issue #203: XML.toXMLString() not recognized by the compiler

2021-12-16 Thread GitBox
Harbs commented on issue #203: URL: https://github.com/apache/royale-compiler/issues/203#issuecomment-995754883 The issue is like you stated that **none** of the XML methods resolves. That causes the following as well: ``` var xml:XML = ; var logStr:String = xml.toXMLString();

[GitHub] [royale-compiler] joshtynjala commented on issue #203: XML.toXMLString() not recognized by the compiler

2021-12-16 Thread GitBox
joshtynjala commented on issue #203: URL: https://github.com/apache/royale-compiler/issues/203#issuecomment-996032275 > xml.Spread.setChildren(objXMLList); > xml.child('Spread')["setChildren"](objXMLList); My latest commit should fix this issue with nested XML member access. --

[GitHub] [royale-compiler] Harbs edited a comment on issue #203: XML.toXMLString() not recognized by the compiler

2021-12-16 Thread GitBox
Harbs edited a comment on issue #203: URL: https://github.com/apache/royale-compiler/issues/203#issuecomment-996041219 Yup. Basically there's a tradeoff here. It's good to know the details. I'll have to write this up in the docs before I forget...  -- This is an automated message from

[GitHub] [royale-compiler] joshtynjala commented on issue #203: XML.toXMLString() not recognized by the compiler

2021-12-16 Thread GitBox
joshtynjala commented on issue #203: URL: https://github.com/apache/royale-compiler/issues/203#issuecomment-996021813 > What defines XML as "dynamic"? When I think of something being dynamic in AS3, I think of accessing arbitrary properties that are not known by the compiler. With

[GitHub] [royale-compiler] Harbs commented on issue #203: XML.toXMLString() not recognized by the compiler

2021-12-16 Thread GitBox
Harbs commented on issue #203: URL: https://github.com/apache/royale-compiler/issues/203#issuecomment-996041219 Yup. Basically there's a tradeoff here. It's good to know the details. I'll have to write this up in the docs before I forget... ;) -- This is an automated message from the

[GitHub] [royale-compiler] Harbs commented on issue #203: XML.toXMLString() not recognized by the compiler

2021-12-16 Thread GitBox
Harbs commented on issue #203: URL: https://github.com/apache/royale-compiler/issues/203#issuecomment-996035694 > Have you tried using the -strict-xml=true compiler option? Bingo. It fixes both issues, but creates other ones: ``` var childName:String =

[GitHub] [royale-compiler] joshtynjala commented on issue #203: XML.toXMLString() not recognized by the compiler

2021-12-16 Thread GitBox
joshtynjala commented on issue #203: URL: https://github.com/apache/royale-compiler/issues/203#issuecomment-996040144 It sounds like you'll need to do some manual string conversions that would normally happen automatically at runtime, in order to make the compiler happy using the stricter

[GitHub] [royale-compiler] joshtynjala edited a comment on issue #203: XML.toXMLString() not recognized by the compiler

2021-12-16 Thread GitBox
joshtynjala edited a comment on issue #203: URL: https://github.com/apache/royale-compiler/issues/203#issuecomment-996032275 > xml.Spread.setChildren(objXMLList); > xml.child('Spread')\["setChildren"](objXMLList); My latest commit should fix this issue with nested XML member