> Dynamically linking to the CRT there doesn't gain you much Not sure what you mean. Linking in dynamic CRT gives you so much that one should even consider whether to even work with a statically-linked CRT for any large project. The biggest issue is the heap CRT uses - if a project uses multiple DLLs, which is pretty much the norm for any large project, then the code linking against static v8 libraries must also use static CRT, which means that it cannot share memory allocations with the rest of the code, which in turn means I cannot even pass around things like `std::string` between these DLLs because if memory is moved to a string constructed in another DLL, it will just corrupt memory. There are other reasons as well, but this one is significant on its own and the bottom line that one has to design a whole interface to move things carefully across the boundary of such DLL. Not a trivial task.
> Node.js) rather than a standalone library. Node.js is not suffering from this because it's using the component build, which uses a CRT in a DLL -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
