Re: [Dltk-dev] 'internal' interpreter preference block

[Andrey Platov <andrey@xxxxxxxxx>]

Hi Jae,

To keep DLTK Core conceptually clear, please could you comment on need to have special 'internal' interpreter. My quick thoughts is that Default interpreter shall be used in cases when you need to ask interpreter to do something outside a project context (or within unknown project context). If project is known - we shall use interpreter bounded to project. This is just general direction.

But your case looks to be slightly different, I guess main reason for you having 'internal' interpreter is to have Perl runtime enviroment to run part IDE code written in Perl. In this case you may be locked by interpreter version and/or required libraries, etc. In this case you definitely shall not rely on Default or any user-configured interpreter. Ideally from my point of view you shall bundle 'internal' Perl execution environment with your IDE and do not expose it to the user at all. Of course your current approach (ask user to configure 'internal' interpreter) will work (also I'm not sure this is convenient for the user), but we'd like to avoid this for other languages. 

Alternatively to bundle Perl environment you may consider to scan "installed interpreters" and choose one that fits your needs (version, libraries, etc). 

As for easy interpreter bundling, in next weeks I'm planning to propose changes to interpreters management and discuss them with committers. Goal is to make DLTK interpreters management more flexible (lie provide good support for interpreters other than executable binaries like JVM ones), easier to use in terms of API and configuration (which shall allow to bundle interpreters in form of OSGi bundles without pain, or retrieve configurations from different sources), etc

Please share your thoughts and if it's possible to introduce 'internal' interpreter at Perl IDE level, please move this code there. If you definitely need some support from core for your implementation - it's fine to leave this code with core, and let's rethink interpreters stuff in future.

Kind Regards,
Andrey


----- Original Message -----
From: "Jae Gangemi" <jgangemi@xxxxxxxxx>
To: "DLTK Developer Discussions" <dltk-dev@xxxxxxxxxxx>
Sent: Wednesday, April 2, 2008 9:06:20 AM GMT +06:00 Almaty, Novosibirsk
Subject: [Dltk-dev] 'internal' interpreter preference block


hello all - 

  i just committed code that can be used to add a preference page that will allow you to select an 'internal' interpreter (the available list comes from the list of installed interpreters) that can be used to execute an arbitrary script from an editor action or in my case, a source parser (and eventually some editor actions). 

  please let me know if there are any problems or questions. 

-- 
-jae 
_______________________________________________
dltk-dev mailing list
dltk-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dltk-dev