#641 perl syntax checking performance

open
nobody
None
5
2016-05-15
2012-02-29
Eric Stob
No

perl syntax checking is making my system crawl when I open a large perl project.(20,000 source files)

Can you please make it so perl syntax checking is not automatic, it is only done on request?

Discussion

  • Jan Ploski

    Jan Ploski - 2012-02-29

    You can untick "Project > Build automatically". Is that not sufficient?

     
  • Eric Stob

    Eric Stob - 2012-09-18

    how can I syntax check just one file? (and the things it depends on recursively)

     
  • Jan Ploski

    Jan Ploski - 2012-09-18

    You can check just one file by saving it. This triggers a syntax check. You cannot check dependencies automatically because EPIC doesn't do any dependency tracking.

     
  • Oliver Trosien

    Oliver Trosien - 2016-05-15

    I think unsetting "Build automatically" is not really an option.

    At work we also have ~10.000 file projects. I found that once you went through the initial "pain" of validating your project, EPIC reacts quite snappy. Still, if you have to change branches frequently, this still causes a lot of files to be rebuilt.

    One possible improvement would be not spawning one perlcritic process per file, but try to batch multiple files into one perlcritic run. Maybe there are other areas where we could avoid spawning perl processes...

     

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

Sign up for the SourceForge newsletter:





No, thanks