jackdaniels has asked for the wisdom of the Perl Monks concerning the following question:
Hello. I am attempting to use Perl EPIC as the IDE for my Perl coding needs. Thus far it has worked alright. The thing is, I am editing a remote code base with it. I ported over the module directories to my local machine so it will stop complaining while editing them. On the old machine, this eventually worked alright (eventually meaning it took it some time... for whatever reason). Now I have a new machine that I lease rolled onto and I am having the same dependency error issues again despite having ported over the same module directory.
If I "use" a file that has any errors anywhere down the line, the editor simply stops checking right then and there, so I pretty much need to use "require" for all of my modules just so it will shut up and check the important sections. Require is a bit limited, so I would like to fix this, but I can't figure out how. I went back and edited the supposedly erroneous dependency. It has no further issues now... that the IDE can see... yet the modules further up the tree that depend on said erroneous module still say that there are "errors in the require", which means that the file that I'm ultimately editing (which depends on those modules) also has this issue. I can literally CTRL+click each use instance and get perl EPIC to pull up a completely error free file that supposedly has errors.
I can't figure out how to make Perl EPIC go back and check the bloody use/require tree to see if there actually is an issue. Changes I make do not appear to be propagating, regardless of what I do. I tried waiting like I did on the old machine and that obviously has not been working. Any ideas? I'm not sure if this is a question that should go here.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Dependency errors in Perl EPIC
by Your Mother (Archbishop) on May 17, 2016 at 17:56 UTC | |
by jackdaniels (Initiate) on May 17, 2016 at 18:20 UTC |