You can assert even in build mode with
qx.core.Assert.assert*
methods.
However thats not usually smart, since asserts makes the code bigger and
slower. You should have it tested in debug mode thoroughly before making
"build" version.
When you use
this.assert*
methods, they work only in when debug is turned on. So yes, you have to
wrap them into
if(qx.core.Environment.get("qx.debug")) {
// code
}
These fragments are stripped from final build completely, so they don't
take up space nor speed... Its well documented in qooxdoo docs.
Mikee
On Mon, Feb 4, 2013 at 1:35 PM, totty <[email protected]> wrote:
> Well I should wrap every statement of assert in a
> if(qx.core.Environment.get("qx.debug") == true)
> there is no other automated way to do it? I don't even know where the
> asserts are within the code...
> and no error is thrown in the build version.
>
>
>
> --
> View this message in context:
> http://qooxdoo.678.n2.nabble.com/Assert-fails-on-build-in-v2-0-1-tp7582716p7582717.html
> Sent from the qooxdoo mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_jan
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
