DefineProperty has landed. I’m sure there are bugs, and the js compile currently generates tons of warnings, but I think it was good enough to push. I filed a bug against GCC for most of the warnings.
Next up, I want to do a big rename of classes and SWCs to better organize things. Opinions are welcome. Before that, I’m going to try to spend a little time fixing up our CI. -Alex On 4/7/15, 11:20 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: >> Google has deprecated @expose so this solution may stop working some >>day. > >I would take that deprecated bit with a grain of salt: > >https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/c >losure-compiler-discuss/pZaodHd0KD0/p767zHJzWO8J > >I read that thread to mean that they want to get rid of the side >effects of @expose in one particular use case, and therefor introduced >a new annotation. It remains the preferred way to prevent property >renaming, it seems. No worries ;-) > >I'm keeping an eye on the compiler's new type inference and ES6 >support progress, I'll keep you posted. > >EdB > > > >-- >Ix Multimedia Software > >Jan Luykenstraat 27 >3521 VB Utrecht > >T. 06-51952295 >I. www.ixsoftware.nl
