I’m less sanguine 2 about whether the current objects in the ImperativeSpike can do everything we need. Basically, once you can store a function in a table and look it up, you can do anything. ![]() I feel quite confident about that aspect, and it’s because I’ve gained enough experience with what’s done so far to be confident that the rest is possible. The basic idea behind yesterday’s work is to drive the program’s parsing and execution entirely from tables that can be provided by code written, not in free Kotlin, but in our DSL, our little language for describing a game world. I certainly hope there is, because I think there’s value in how I think and work, but honestly, whether this is a concert, or just practice, I enjoy playing.īut I do hope people are reading and enjoying, and it’s wonderful when I hear from them. That’s why I don’t really care too much whether there’s anyone out there reading it. I enjoy learning a new system, at least after I get past those early days when you have no idea what’s going on, I enjoy crafting code neatly, and I enjoy writing about it. I think it’s fair to say that the main reason is that I can, and I enjoy it. Early DIgression I want to address again why I’m doing this. Nearly every method, other than one or two that are still not table-driven, has come down to one line of code. What I like about the Imperative and associated classes is that it has turned out to be quite neat and tidy. After a bit of testing and enhancing the tables, I’ll think about whether and how to use it. In reviewing the code, I’m not sure what else it needs to do the job.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |