On 11/28/2011 05:24 PM, Benjamin Dreux wrote: > Hi, > > In such situation can we ignore this warning ?
You can always ignore warnings, if you have convinced yourself that the indicated case is ok for you :). Warnings try to draw your attention to something which is not bad in itself, you just should know what you are doing. If you do and decide to keep it the way it is, you can silence the warning in many cases. In the case of a qx.core.Environment call with a non-literal first argument you are just missing the opportunity to optimize this call, but you will always have working code. If there are no dependencies or costly calculations guarded by the call to qx.core.Environment, you're not even paying a penalty for not optimizing it. On the other hand, even a small penalty might be worth the price if your business logic becomes cleaner by using a variable in place of a literal. T. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
