Viewing profile — laurenth

A shell is almost always used to setup the bootstrap environment, so the dependency on a shell is more or less always there. Otherwise, something special with POSIX shell is its la…

Author here, > assuming the resulting shell script is as inscrutably as binary executable It's quite the opposite, pnut generates shell code that's close to the original C code to …

We haven't found this to be an issue for Pnut. One of the metric we use for performance is how much time it takes to bootstrap Pnut, and dash takes around a minute which is about t…

That's the idea! As you point out, it moves the trust from the binary to the shell executable, but the shell is already a key piece of any build process and requires a minimum leve…

You're right, thanks for the bug report. It should now be fixed :)

It seems ShellCheck errs on the side of caution when checking arithmetic expansions and some of its recommendations are not relevant in the context they are given. For example, on …

From our experience, ksh is generally faster, and dash sits between ksh and bash. One reason is that dash stores variables using a very small hash table with only 37 entries[0] mea…

One of the example we include is a base64 encoder/decoder: https://github.com/udem-dlteam/pnut/blob/main/examples/compiled/base64.sh It doesn't support NULs as you pointed out, but…

Author here, That's correct! Unlike Bash and other modern shells, the POSIX standard doesn't include arrays or any other data structures. The way we found around this limitation is…

Author here, Because all shell variables in code generated by pnut are numbers, variables never contain whitespace or special characters and don't need to be quoted. We considered …