Hi Josh, the problem is that sometimes I can't even say what's the cause of the npes. Most of them occured inside the compiler and from the context variables I can only guess what's going on. And I would probably have to open a big 2 digit number of issues, I would like to prevent that. I guess as soon as I have ported things to maven I can start using some of my static code analysis tools and start mass-producing test-cases ;-)
But I would like to suggest to start thinking about the case that people do things wrong. FlexJS works well if you are on the correct path, but the code currently simply can't cope well with errors. Chris ________________________________________ Von: Josh Tynjala <joshtynj...@gmail.com> Gesendet: Freitag, 18. März 2016 15:59 An: dev@flex.apache.org Betreff: Re: [FALCON] Definitely needs some love ... I think the first step is documenting these null pointer exceptions as they are encountered. Opening bug reports in JIRA seems like the right course of action. - Josh On Fri, Mar 18, 2016 at 7:09 AM, Christofer Dutz <christofer.d...@c-ware.de> wrote: > Hi, > > > Well I think one thing we definitely need to work on, is making Falcon and > FalconJX a lot more robust. During my work on Mavnizing everything I > continuously encounter NullPointerExceptions all over the place. It seems > that most of the code seems to currently work if everything is correct, but > fail miserably with NullPointers if you are not 100% correct. Guess this > will cause a lot of frustration with our users. > > > Chris >
