Why would we need to manually load a LanguageRuntime plug-in? The expression parser just knows what language it is dealing with and the RenderScript expression parser should just request the language runtime plug-in when and only when it needs it.
What you are trying to accomplish? Can you give me a workflow of what you are thinking? Greg > On Apr 21, 2015, at 3:06 AM, Colin Riley <[email protected]> wrote: > > There is no need for it to be always created. But at present, I can't see > anywhere for the user to load a language runtime explicitly. Would adding a > language load command to the plugins group be suitable? > > I'm thinking C++ going into other language bindings and back again. For the > user, having these plugins automatically loaded on some sort of discovery > event would be ideal. However, having a 'plugin language load <language > name>' command so the user can set up their environment is the next best > thing. I can add this command if you agree (will simply GetLanguageRuntime() > on the process, ensuring non-null is returned) and put up a patch. > > Colin > > > REPOSITORY > rL LLVM > > http://reviews.llvm.org/D9002 > > EMAIL PREFERENCES > http://reviews.llvm.org/settings/panel/emailpreferences/ > > _______________________________________________ lldb-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits
