R7: Like falling into a black hole
Gather 'round, kiddies! It's time for our daily task list update! Yayy!
- Integrate new features with the assembler and bytecode systems
Pop the parser stack correctly to improve error responses
- Fix some bugs in nested response map support
Improve syntax for initializing nested structures Improve syntax for accessing nested structures Organize ParserState class a bit better Add support for empty lists Change from using char to a Byte typedef to highlight code that manipulates single bytes
- Perform complete code review for exception safety, documentation, code cleanliness, error handling robustness, and elimination of hardcoded strings/magic numbers
- Complete code review of all example programs to ensure they use the latest syntax and features
As you can see, this is slightly shorter than the last task list, but it also contains a couple of extra things that snuck their way in and caused havoc.
Release 7 continues to be a tantalizing prospect: just when I think I'm ready to quit fixing bugs and making tiny tweaks, I discover another set of fairly significant problems. Bummer.
On the plus side I got plenty of stuff done over the weekend, so at least progress continues to be made. On the down side, though, I now have to go back to work again for the week, which means very little time and energy for Epoch.
I'll be hacking away most of the night, I suspect, and we'll see what I can manage to get done before the work week kicks in. After that, it's anybody's guess.
Oh, be sure to check out the Google Code page for Epoch. I'm (slowly) putting together a complete description of the language, it's design philosophy and goals, and current capabilities. I'll continue posting most of my updates here, but anything significant (like, say, shipping a release) will get a news entry on the GC site.
This is of course a perfect opportunity to remind all my awesome readers that Epoch is an open-source project, and additional contributors would be very welcome indeed.
Just a hint [razz]