On Hiatus : Learning from Handmade Hero before continuining #44
Ed94
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This library was my first major attempt to really try a different path to the programming style I have to done in either Unreal/Godot, or I had done traditionally for other personal projects.
I have been interested in the handmade philosophy for a couple of years now (peripherally). This month I've decided to eat the bullet and go "all-in". So I've been doing handmade hero now as my main side-project off work, and plan to come back to this as soon as I feel comfortable switching back with what I learn.
The library is in a pretty good state, it can technically generate the vast majority of code people would want todo, the next phase is really beyond the original scope for it. However, there is a lot of potential with the next phase I see for this library and want to come at it when I got other goals squared away. For now at least I'll cleanup what I have in dev and possibly update main if possible before pausing.
So far I reordered the roadmap a bit from what my original plans were. First I wanted to do was get the library fully validating with the
AST::is_equalfunction before redesigning anything or adding new features. Right now coming back to close this off properly I realized that what I need to instead do is kill off the tasks left to work on what would really make my velocity faster : A visual AST debugger.To make that happen without having to refactor/rewrite the debugger, I need to finalize the AST data layout, do some of the last improvements or fixes to the debug_string, and make sure the parser can fail and continue on errors:

This comes from the realization that most of the time I spend on this project is debugging the parser now-days and trying to make a string debug to show failures along with other meta-data is actually more difficult than just setting up a graphical debug of the AST tree itself.
I've done this before in godot for another language project:

I'll do something similar for this library; this time with raylib, and probably with a few more features to introspect properly.
Beta Was this translation helpful? Give feedback.
All reactions