Enhancement request: Have same parameters on PCTCompile and PCTCompileExt

[GoogleCodeExporter]

Changing a PCTCompile task to PCTCompileExt requires a number of changes.
This could be limitted if both tasks would have the same interface /parameters 
. They could silently, if not verbose, ignore the options that are not relevant.

Related to #48

e.g. PCTCompileExt will fail if there is a progPerc

What version of the product are you using? On what operating system?
Version 187

Alternatave solution :
Add numThreads to PCTCompile and make numThreads=1 identical to the current 
PCTCompile

Original issue reported on code.google.com by cverbi...@gmail.com on 5 Sep 2014 at 8:57

[GoogleCodeExporter]

I'd like to refactor the code in PCTCompile and PCTCompileExt, and especially 
use the same procedures in both cases.
I just need to find some time...

Original comment by g.quer...@gmail.com on 3 Oct 2014 at 12:24

• Added labels: ****
• Removed labels: ****

[jakejustus]

If somebody's willing to help on that, that would be good !

[jakejustus]

Whohooo !