Harbs, I think that is only for debug. I don't think they should add bulk to the release code. At least they do not in the default settings for GCC optimisation. You will see the definition of the constant only once and inline replacement is used for the value (with a short name global variable) everywhere. The only extra cost of a constant seems to be a lookup reference that may be added. It seems quite minimal.
If you do a search for both the constant value e.g. 'change' or the the name of the constant (e.g. FORM_SAVED ) in the release output you should only ever see it once whichever way you do this. On Wed, May 24, 2017 at 1:28 PM, Harbs <harbs.li...@gmail.com> wrote: > Huh? Why would tests be necessary? > > Like I already said; constants add much more bulk to the JS source code. > Try it and you’ll see… > > > On May 23, 2017, at 5:53 PM, Justin Mclean <jus...@classsoftware.com> > wrote: > > > > Have you done any tests to show this is the case? > >
