-
EPIC doesn't contain any native code, so it should work on x64. I recall having had problems with stability of x64 Java+Eclipse (not EPIC), but it was a long time ago.
You should check whether any errors appear during Eclipse startup in the error log (workspace/.metadata/.log).
2009-11-30 00:35:36 UTC in EPIC - Eclipse Perl Integration
-
You're looking at the wrong context menu. The one you are interested in and portrayed in http://www.epic-ide.org/guide/images/variables_view.gif can be opened by clicking on the little arrow symbol in the top-right corner of the view.
2009-11-23 20:42:22 UTC in EPIC - Eclipse Perl Integration
-
EPIC uses the call InetAddress.getLocalHost().getHostAddress(), which in turn goes through the resolver library, which in turn relies on what is configured in /etc/hosts. Try the command 'hostname' in shell, then ping that hostname. If the reported IP address is wrong, edit /etc/hosts to fix it.
2009-11-11 17:29:25 UTC in EPIC - Eclipse Perl Integration
-
There's no solution and no dynamic inspection. Dynamic means that the code to be inspected would have to be executed first, but there's no way to tell in general what to execute and what not and which preconditions have to be true in order for the execution to be useful.
If you need reliable inspection in an IDE, you should use a strongly typed language (such as Java), and even so you'd find...
2009-11-06 23:36:21 UTC in EPIC - Eclipse Perl Integration
-
If you look at the source code of DBI.pm, you will find there is no 'sub prepare' in there. It is added dynamically at run time, thus not available to static inspection.
2009-11-06 21:35:33 UTC in EPIC - Eclipse Perl Integration
-
The Eclipse way of doing things is to create a launch configuration per executable (and arguments, and environment variables etc.) that you want to run. This also applies to Perl scripts. Then you can use the Run/Debug button to re-launch last script (browse older threads for how to set up the Launching preferences for this to always work). You can also select from among the last few launch...
2009-11-05 23:43:23 UTC in EPIC - Eclipse Perl Integration
-
Does it also happen with the most recent version of EPIC (0.6.35)?.
2009-11-02 17:44:20 UTC in EPIC - Eclipse Perl Integration
-
I can't quite reproduce the behavior your described, but it is worth noting that the source formatter always works on the whole file, not on the current selection. Perhaps it explains what is happening in your case?.
2009-11-02 17:23:00 UTC in EPIC - Eclipse Perl Integration
-
When you run the PerlDoc action on function 'print', EPIC executes a snippet of code using the Perl interpreter configured in Preferences. The snippet is as follows:
use Env qw(@PERL5LIB);
splice(@PERL5LIB, 0, 0, @INC);
exec('perldoc -t -f "print"');
So check that PERL5LIB is set correctly and that the program 'perldoc' from the new Perl installation can be...
2009-11-01 17:01:37 UTC in EPIC - Eclipse Perl Integration
-
Do you mean that the process is there without you having launched anything? If so, it could only be the syntax validator. However, EPIC launches a new process per each validated file. So it's not really a background process that should grow in size over time - unless you have a source file which causes perl -c to go crazy (seems improbable).
Can you figure out the arguments of that process to...
2009-10-29 10:19:24 UTC in EPIC - Eclipse Perl Integration
