compile options to prevent optimization of private members

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

compile options to prevent optimization of private members

Alper Ortac

I want to disable optimization of private members. According to the docs

http://manual.qooxdoo.org/2.0.x/pages/tool/generator_config_ref.html#compile-options

i created a new job without the optimize privates option:

 

                "jobs": {

                               "build-noprivate" : {

                                               "extend" : ["build"],

 

                                               "compile-options" : {

                                                               "code" : {

                                                                              "optimize" : ["basecalls", "comments", /*"privates",*/ "strings", "variables", "variants", "whitespace"]

                                                               }

                                               }

                               }

                }

 

If i run that task, everything seems to build just fine. But, if I try the application and want to access a private variable of an extended class I still get an error that it is not defined. Is there something wrong in my config?


------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: compile options to prevent optimization of private members

Alexander Steitz

Hi,

 

you do not need to create an own job achieving this. Adding the global macro “OPTIMIZE” is easier.

 

You have to insert the following into your global “let” block:

 

--snip--

"OPTIMIZE" : ["basecalls", "comments", "strings", "variables", "variants", "whitespace"]

--snip--

 

And that should do it.

 

Regards,

  Alex

 

From: Alper Ortac [mailto:[hidden email]]
Sent: Wednesday, November 14, 2012 2:49 PM
To: [hidden email]
Subject: [qooxdoo-devel] compile options to prevent optimization of private members

 

I want to disable optimization of private members. According to the docs

http://manual.qooxdoo.org/2.0.x/pages/tool/generator_config_ref.html#compile-options

i created a new job without the optimize privates option:

 

                "jobs": {

                               "build-noprivate" : {

                                               "extend" : ["build"],

 

                                               "compile-options" : {

                                                               "code" : {

                                                                              "optimize" : ["basecalls", "comments", /*"privates",*/ "strings", "variables", "variants", "whitespace"]

                                                               }

                                               }

                               }

                }

 

If i run that task, everything seems to build just fine. But, if I try the application and want to access a private variable of an extended class I still get an error that it is not defined. Is there something wrong in my config?


------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: compile options to prevent optimization of private members

Alper Ortac

That did the trick, thanks alot!

 

From: Alexander Steitz [mailto:[hidden email]]
Sent: Mittwoch, 14. November 2012 15:50
To: qooxdoo Development
Subject: Re: [qooxdoo-devel] compile options to prevent optimization of private members

 

Hi,

 

you do not need to create an own job achieving this. Adding the global macro “OPTIMIZE” is easier.

 

You have to insert the following into your global “let” block:

 

--snip--

"OPTIMIZE" : ["basecalls", "comments", "strings", "variables", "variants", "whitespace"]

--snip--

 

And that should do it.

 

Regards,

  Alex

 

From: Alper Ortac [[hidden email]]
Sent: Wednesday, November 14, 2012 2:49 PM
To: [hidden email]
Subject: [qooxdoo-devel] compile options to prevent optimization of private members

 

I want to disable optimization of private members. According to the docs

http://manual.qooxdoo.org/2.0.x/pages/tool/generator_config_ref.html#compile-options

i created a new job without the optimize privates option:

 

                "jobs": {

                               "build-noprivate" : {

                                               "extend" : ["build"],

 

                                               "compile-options" : {

                                                               "code" : {

                                                                              "optimize" : ["basecalls", "comments", /*"privates",*/ "strings", "variables", "variants", "whitespace"]

                                                               }

                                               }

                               }

                }

 

If i run that task, everything seems to build just fine. But, if I try the application and want to access a private variable of an extended class I still get an error that it is not defined. Is there something wrong in my config?


------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: compile options to prevent optimization of private members

John Spackman-3
In reply to this post by Alper Ortac
You need to prefix the "optimise" key with "=" otherwise the generator merges your list with it's existing list (i.e. no change ).  Try:

"code" : {

                            "=optimize" : ["basecalls", "comments", /*"privates",*/ "strings", "variables", "variants", "whitespace"]

        }


John
From: Alper Ortac <[hidden email]>
Reply-To: qooxdoo Development <[hidden email]>
Date: Wednesday, 14 November 2012 13:49
To: "[hidden email]" <[hidden email]>
Subject: [qooxdoo-devel] compile options to prevent optimization of private members

I want to disable optimization of private members. According to the docs

http://manual.qooxdoo.org/2.0.x/pages/tool/generator_config_ref.html#compile-options

i created a new job without the optimize privates option:

 

                "jobs": {

                               "build-noprivate" : {

                                               "extend" : ["build"],

 

                                               "compile-options" : {

                                                               "code" : {

                                                                              "optimize" : ["basecalls", "comments", /*"privates",*/ "strings", "variables", "variants", "whitespace"]

                                                               }

                                               }

                               }

                }

 

If i run that task, everything seems to build just fine. But, if I try the application and want to access a private variable of an extended class I still get an error that it is not defined. Is there something wrong in my config?

------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov_______________________________________________ qooxdoo-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel