asm() has some odd behavior of how escaping and so forth works - it's designed for typical inline assembly, not JS. EM_ASM is in practice easier to use for that reason.
Also, expanding the code inline can break asm.js validation - it's arbitrary JS - so we expand it outline. I guess there might be a use case for actually expanding inline though, for things like `debugger;`. But, perhaps we should just add an intrinsic emscripten_debugger() that you would call. Is there anything aside from `debugger;` like this? - Alon On Tue, Mar 4, 2014 at 11:55 PM, Chad Austin <[email protected]> wrote: > I'm playing with fastcomp to see what it would take to get a few embind > demos running in asm.js. > > It was pretty convenient to put asm("debugger"); in Emscripten output, but > now asm() doesn't work. You have to use EM_ASM, which breaks into the > debugger a couple entries down in the stack, which is just a bit less > convenient. > > Is there a particular reason why? > > -- > Chad Austin > Technical Director, IMVU > http://engineering.imvu.com <http://www.imvu.com/members/Chad/> > http://chadaustin.me > > > -- > 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/groups/opt_out. > -- 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/groups/opt_out.
