#87 errors are erroneous and erratic

closed-works-for-me
LeO
Core (65)
5
2004-11-10
2004-08-25
No

First reported in forum on 2004.05.27 by me (http:
//sourceforge.net/forum/forum.php?
thread_id=1082953&forum_id=258688)...
then reported by Remco Douma on 2004.08.13 (https:
//sourceforge.net/forum/message.php?msg_id=2712764)..
.

Summary: I am consistently getting erroneous errors,
whether Unix or Windows line endings are used. First with
eclipse 2.1.3 (and epic 0.2.0), I then upgraded to eclipse
3.0 (and epic 0.3.0) and still get bogus (but different!)
errors. Also, trying the same project on different
computers (from the same eclipse .metadata) yields
different bogus errors. Finally, I'll mention for
completeness that my Java code runs flawlessly in
eclipse--no bogus errors. Any chance this is a memory
problem? I run only a 256MB machine.

Having seen no further posting since the request for
sample files a week or so ago, I took another look at the
issue. I closed all projects except my Perl one, and still
had lots of erroneous errors. I closed that project and
created a new test project. With just one file in
it--attached--the problems are still present. My system
shows 3 errors--all erroneous. If I then delete the large
comment block near the top of the file, they all go away.
(Depending on which pieces you delete, different things
happen.)

Discussion

<< < 1 2 3 4 (Page 4 of 4)
  • LeO

    LeO - 2004-11-10
    • status: open --> closed-works-for-me
     
  • LeO

    LeO - 2004-11-10

    Logged In: YES
    user_id=703323

    I somehow going to loose my interest on this ticket. Perhaps
    somebody else could deal with it. Main reasons for this are
    the following:

    1) You don't know the obvious things, like how to set the
    perl-include path.
    2) The check-method in Eclipse is exactly the same as
    DOS-shell. So, if there is one a problem and in another not,
    this couldn't be. (Not very clear is, if you changed to CGI2
    or not and the influence of the behaviour.)
    3) You are not willing to upgrade the Perl-version.

    The only way I currently see to solve this problem is to
    upgrade your Perl-version, what you are not willing to do.

    I'm out of idea. Sorry.

     
  • Remco Douma

    Remco Douma - 2004-11-24

    Logged In: YES
    user_id=290130

    As the person who originally submitted this problem, I am
    happy to report that the problem has "disappeared" after I
    upgraded to Perl 5.8 (I was working on 5.6.1).

    So: indeed, upgrading the Perl version solves the problem
    (at least it did in my case).

    I am now a happy user of E.P.I.C.!

     
  • Michael Sorens

    Michael Sorens - 2004-11-24

    Logged In: YES
    user_id=800488

    Could you be more specific please--5.8.what? I have had 5.8.0
    all along, as I reported. It would be helpful to know if you are
    using a later one.

     
<< < 1 2 3 4 (Page 4 of 4)

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks