On 6/14/22 10:11, Nick Bowler wrote:
The resulting config.h is correct but pa.sh took almost 1 minute to run the configure script, about ten times longer than dash takes to run the same script. More than half of that time appears to be spent just loading the program into pa.sh, before a single shell command is actually executed.
Ouch. Thanks for looking into this, and sorry it took so much of your time. It appears that PaSh itself isn't suitable for prime-time use. This isn't too surprising, though, as it's a research project and I wouldn't expect it to compete with production shells. The main question here is whether the ideas of PaSh are good ones for improving Bash.
