On 11/28/2011 01:27 PM, John Spackman wrote:
> Hi,
>
> I'm getting the warning 'qx.core.Environment call without literal
> argument' because I want to use environment settings to configure a
> library; I'm aware of bug #5336 and #5307 but not sure if I can safely
> ignore these warnings in my own code - e.g. is the warning because the
> generator cannot remove unnecessary code etc, or should I use a
> different mechanism for passing config values to the library?
Mh, I don't think it has anything to do with configuring libraries.
qx.core.Environment calls are basically lookup's, so they cannot pass
anything.
The warning simply triggers when you e.g. call
var foo="my.setting";
qx.core.Environment.get(foo); // call with non-literal argument
instead of
qx.core.Environment.get("my.setting"); // call with string literal
As you guessed, the non-literal call cannot be optimized if "my.setting"
is given in the config.
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
