Re: [FALCON] don't warn on assignment in while (condition) body

On 1/1/15, 2:43 AM, "Left Right" wrote: >if I wanted to convince someone >to try Falcon, what would be the good argument to do so? IMO, if you have a bug you want fixed in Falcon or a question about it you want answered, you’ll find several folks on this mailing list who might be able to help.

Re: [FALCON] don't warn on assignment in while (condition) body

But > > > -ignore-problems=org.apache.flex.compiler.problems.AbstractSemanticProblem > > doesn't currently cause all subclasses of AbstractSemanticProblem to be > ignored, does it? > > - Gordon > > > Date: Thu, 1 Jan 2015 15:50:11 -0500 > > Subject: Re

RE: [FALCON] don't warn on assignment in while (condition) body

to search the source for the class representing a particular > > problem is to search for part of the English message. But you have to be > > careful not to search for something that is getting dynamically substituted > > for a placeholder in the string. > > > > > >&

Re: [FALCON] don't warn on assignment in while (condition) body

careful not to search for something that is getting dynamically substituted > for a placeholder in the string. > > > >> I don't think most people would even go as far as looking into the > source code for ways to void a warning message. > > > > Numeric problem co

Re: [FALCON] don't warn on assignment in while (condition) body

r as looking into the > source code for ways to void a warning message. > > Numeric problem codes seem like the way to go, if we don't already support > them. > > - Gordon > > > Date: Wed, 31 Dec 2014 11:56:45 +0200 > > Subject: Re: [FALCON] don't warn on assignm

Re: [FALCON] don't warn on assignment in while (condition) body

urce >> code for ways to void a warning message. > > Numeric problem codes seem like the way to go, if we don't already support > them. > > - Gordon > >> Date: Wed, 31 Dec 2014 11:56:45 +0200 >> Subject: Re: [FALCON] don't warn

RE: [FALCON] don't warn on assignment in while (condition) body

to go, if we don't already support them. - Gordon > Date: Wed, 31 Dec 2014 11:56:45 +0200 > Subject: Re: [FALCON] don't warn on assignment in while (condition) body > From: olegsivo...@gmail.com > To: dev@flex.apache.org > > Could this be improved to have a

Re: [FALCON] don't warn on assignment in while (condition) body

Could this be improved to have a better interface?.. Grepping through the code I get 1388 hits for org.apache.flex.compiler.problems in Java files alone. No one would think of this as being an easy way to find an offending warning... But I don't think most people would even go as far as looking int

Re: [FALCON] don't warn on assignment in while (condition) body

The falcon compiler and the (old) mxmlc compiler handle errors and warnings differently. In the mxmlc compiler a message is always an error/warning/info message at creation. In falcon, messages have a default severity but can be treated as an error, warning, or ignored. The configuration options to

[FALCON] don't warn on assignment in while (condition) body

I don’t know for sure. Maybe Gordon or Darrell know if warning suppression is supposed to work in Falcon. On 12/30/14, 1:35 AM, "Left Right" wrote: >I looked into mxmlc -help warnings but I don't see an option to void >the warning issued on assignment inside while (and maybe other such >places)

Falcon don't warn on assignment in while (condition) body

I looked into mxmlc -help warnings but I don't see an option to void the warning issued on assignment inside while (and maybe other such places). Is there one, or it simply isn't implemented yet? Thanks!