| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
As we near the end of SoC, libbash is approaching a point where it's a |
| 5 |
solid base. We knew going into this project that implementing the |
| 6 |
entirety of bash in one summer wasn't going to happen |
| 7 |
|
| 8 |
This past week, my mentor and I worked out a few more details about bash |
| 9 |
builtin functionality. |
| 10 |
|
| 11 |
There is a system for writing and inheriting bash builtins. There is no |
| 12 |
established system for keeping track of the builtins or a builtin |
| 13 |
Factory yet, but the framework to implement all the builtins is there. |
| 14 |
|
| 15 |
The grammar is more or less complete, and the grammar file has been |
| 16 |
cleaned and commented so any debugging that needs to happen can be |
| 17 |
efficient and easily understood. There are no missing features, and the |
| 18 |
features there seem to work correctly. |
| 19 |
|
| 20 |
We've also generated a backlog that, once it is completed, should result |
| 21 |
in code that allows us to generate metadata. This is a huge goal that |
| 22 |
requires most of bash to be rewritten, but having it broken into |
| 23 |
manageable stories is a wonderful start (and decidedly less depressing |
| 24 |
than "implement Bash... GO!"). |
| 25 |
|
| 26 |
This week I'm focusing on documentation and the build system for the |
| 27 |
most part. The goal is that if we bring other developers into this |
| 28 |
project, the framework isn't a mess and is easy enough for them to work |
| 29 |
with. |
| 30 |
|
| 31 |
Nathan |
| 32 |
-----BEGIN PGP SIGNATURE----- |
| 33 |
Version: GnuPG/MacGPG2 v2.0.14 (Darwin) |
| 34 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
| 35 |
|
| 36 |
iEYEARECAAYFAkxhbwwACgkQSkGJyeMPBy5TGQCfY2iGN8nltBcNlRCnI9tnuix0 |
| 37 |
8YsAoNtZ0u6vaN+bDvppDn2T9XMPKHvR |
| 38 |
=yC4n |
| 39 |
-----END PGP SIGNATURE----- |
Archives