The most typical Closure issue comes when closure mixes up and minifies a property access that it should not have. The only solution to debugging exactly which that I've found is to tediously cross-examine original and minified output to deduce what the bad transformation was. The simplest way to prohibit closure from performing a minification of a member access is then to use the string property lookup, i.e. instead of object.property, write object['property'] to force closure to avoid transforming the expression. If you search the emscripten commit log for messages with a comment "closure", you can find instances of closure related fixes that have been done to the emscipten provided libraries, which can give you examples of what kind of transformation closure typically gets wrong.
tiistai 21. lokakuuta 2014 wolfviking0 <[email protected] <javascript:_e(%7B%7D,'cvml','[email protected]');>> kirjoitti: > Hi, > > I have my own library inside emscripten for support WebCL API. Everything > work, but when I build my sample using --closure 1, the code are not > working because some API function are changed by the closure. > > I suppose I do something wrong. Can I have some suggestion please for make > my code compatible with closure ? > > Tony > > -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
