I see
It's also a lot less taxing (code and process time) doing quick registry reads than it is opening, reading, parsing, converting from and closing a JSON file on each run in C#.
Makes testing a whole lot easier as well.
Hmm, doubtful
It also ensures the configuration is always in a single, specific location, so it can be read and modified without having to figure out where the installation is located (by parsing and then searching each PATH for the berrybrew.exe binary, then loading the file from the data directory).
$HOME/.berrybrew is just as specific and doesn't require much figuring out
In reply to Re^3: berrybrew, the Perlbrew for Windows v1.30 released!
by Anonymous Monk
in thread berrybrew, the Perlbrew for Windows v1.30 released!
by stevieb
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |