Yeah, I also think EPIC is useless in complex projects until there will be a way to setup custom builder (using perl, not java, please! :)).

In addition to perl modules there a lot of other "build environments" which require support from IDE even for syntax checking. Just two examples:

  1. html templates with perl code inside (especially one which use custom html templating system :))
  2. small files with pieces of perl code designed to be eval'ed in some preconfigured environment: config files, web site parsers, etc. etc. etc.

Also EPIC must support all 'advanced' perl features like attribute handlers - debugger in version 0.4.0 just die when try to open any (script which use) perl module which use Perl6::Export::Attrs (recommended in PerlBP book). (It dies in INIT{} block, so maybe this bug isn't related to attribute handlers, but INIT{} blocks is another advances perl feature which must be supported.)

BTW, just for fun, I notice very cool bug in EPIC bugtracking system: trying to check syntax of this script 

BEGIN { 1 while 1 }

[download]
if fork many perl processes which use 100% CPU and never kill them. :)

In reply to Re^2: Getting started with Eclipse & EPIC by powerman
in thread Getting started with Eclipse & EPIC by g0n

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.