Data and engineering.
Joined December 2016
- Tweets 47
- Following 68
- Followers 13
- Likes 102
2 Photos and videos
19 Feb 2020
#100DaysOfCode #cplusplus Day 10
Added an operation code and some debugging methods for checking chunks for constants. These will allow the virtual machine to deal with literals (ex: print 1;). 10 days in, 90 to go. Looking forward to see how the language shapes up from here 😀
5
3
17 Feb 2020
#100DaysOfCode #cplusplus Day 9 - Added a ValueArray type to hold constants for chunks in memory. I'll start working on an interface soon so that I don't have to expose the arrays to the dangerous public. 😁 Just a day or two away from beginning work on the virtual machine now!
1
1
17 Feb 2020
#100DaysOfCode #cplusplus Day 8:
Finally, some feedback! Created a chunk, wrote an operation code to it, disassembled it to verify the op code, and then freed the memory.
Is it impressive? Nope! But now I at least have some visual feedback now to see if things work! 😁
1
2
16 Feb 2020
#100DaysOfCode #cplusplus Day 7:
Forgot to post my update yesterday, so here it is. Added methods to disassemble chunks of code to peek at them. Not super interesting for using the language, but definitely useful for debugging. I'll be working on more later today for day 8.
6
2
14 Feb 2020
#100DaysOfCode #CPlusPlus Day 6:
Wrote the memory allocation functionality today. Faced an interesting problem for scaling the dynamic memory array: do you scale by a larger num and sacrifice memory on small chunks, or smaller num and make more memory accesses on large ones? 🤔
1
1
4
14 Feb 2020
Right now I start with 8 bits and double the array size if the code chunk needs to be larger. So if 9 bits are needed, we waste the additional 7 bits. But if I scale by, say, 4 bits and needed 16 bits, I'd have to grow the array twice instead of once.
14 Feb 2020
#100DaysOfCode #CPlusPlus Day 5:
Finished implementing tokens for the language, but planning to take a pivot soon. I'll be implementing a bytecode compiler soon, instead of an interpreter. I decided to go this route in order to better understand the compilation process.
2
6
13 Feb 2020
#100DaysOfCode #CPlusPlus
Day 4:
Spent most of today trying to decide how to implement Tokens for literals which can be of various types (bool, null, int, string). I'm hoping that within the first two weeks I can have enough to make a gif of my language in action. More to come!
5
2
12 Feb 2020
#100DaysOfCode #CPlusPlus
Day 3:
Today I created basic error handling for my language. I added an enum TokenTypes for the various tokens in the lang (keywords like "func", operators like , =, !=, etc), then wrapped it all in a Token class which holds all the info about them.
3
2
10 Feb 2020
#100DaysOfCode Day 2:
I've begun work on two things in my language today. Firstly, the interactive interpreter. Currently it just continuously reads from standard input and stores the data in a string. I've also begun work on my Scanner, so I can do useful things with the input.
1
1
10 Feb 2020
#100DaysOfCode C Day 1:
Wrote the main function for my language (yet to be named), which takes a file path as an arg, reads the file, and stores the data in a vector.
Next up tomorrow: if no args are given, open an interactive interpreter.
More to come over the next 99 days!
7
6