So BAH to polymorphism. And just plain BAH in general.
I would have finished the Stack Based Epoch changes tonight, but then I realized that I technically have several polymorphic built-in functions, and my head just doesn't want to deal with polymorphism and stacks.
So BAH to polymorphism. And just plain BAH in general.
So BAH to polymorphism. And just plain BAH in general.
Previous Entry
Stack-based Epoch: round 1
Next Entry
Burning up, burning down, burning out
Comments
August 17, 2008 12:22 PM
I don't mean to bother you with C++ questions, but I've been studying the code for Epoch (the "old" version), and I noticed that in your Variable class you used two public/protected access modifiers. Is there any practical reason for this, or is it merely an aesthetical detail?
I'll have a play with the language after I've scrutinized the source code, as it could be valuable learning [grin] But, is this what the syntax will look like, or is it just a way of testing the VM?
I'll have a play with the language after I've scrutinized the source code, as it could be valuable learning [grin] But, is this what the syntax will look like, or is it just a way of testing the VM?
August 17, 2008 12:23 PM
Advertisement
Latest Entries
A Few Farewells
14505 views
Code Reuse In Actual Practice
16368 views
Source-Level Debugging For Epoch Programs
4882 views
Using Poison to Reverse Engineer Code
152320 views
Using Poison to Reverse Engineer Code
3519 views
Debugging Information Success
2841 views
Debugging Information Success
5359 views
Debugging Epoch Programs
3055 views
Debugging Epoch Programs
6740 views
Epoch 64-bit compiler progress
2543 views
Advertisement
I'll have a toy with the language after I've scrutinized the source code, as it could be valuable learning [grin] But, is this what the syntax will look like, or is it just a way of testing the VM?