(no subject)
I actually have gotten some work done over the last two days. Not much, but it's a start, and I'm going to write about it because that was part of the idea. This entry is super nerdy so you can basically skip it if you want.
Most of my work was on a dorky little project that I work on every now and then. I call it 'Panacea'. It's a virtual machine with a very ASM-ish instruction set, encoded as 4x32bit instructions. It's all very preliminary and such but the idea is to make it as speedy as possible and easy to drop into another program. I'd also like to add that it is already endian-neutral; it does byteflipping on load so it can deal with bytecode compiled anywhere.
Why? Well... it's cool. It's fun to manually write bytecode with a hexeditor while I'm testing out instructions. Once I get a decent VM going, I'll write myself an assembler and, eventually, I can write myself some compilers that will compile into Panacea bytecode. Then I can use it for projects that need internal scripting (if I want) and, get this, I can actually write the scripting in any language that I make a compiler for. As long as it compiles to the Panacea bytecode, it can be used by an app that embeds the Panacea VM. So, theoretically it could be useful, some day. Mostly, it's just fun to mess around with at the moment, though.
I have another idea that is still in a sort of infant state so I don't want to talk about it too much. It'd be a website/community thingy that would be pretty cool if it doesn't get botched up in the implementation and early stages of use. I'll think more about it and maybe post more if I decide to go ahead with it (or if I decide not to go ahead with it and figure someone else might have a use for the idea).
Most of my work was on a dorky little project that I work on every now and then. I call it 'Panacea'. It's a virtual machine with a very ASM-ish instruction set, encoded as 4x32bit instructions. It's all very preliminary and such but the idea is to make it as speedy as possible and easy to drop into another program. I'd also like to add that it is already endian-neutral; it does byteflipping on load so it can deal with bytecode compiled anywhere.
Why? Well... it's cool. It's fun to manually write bytecode with a hexeditor while I'm testing out instructions. Once I get a decent VM going, I'll write myself an assembler and, eventually, I can write myself some compilers that will compile into Panacea bytecode. Then I can use it for projects that need internal scripting (if I want) and, get this, I can actually write the scripting in any language that I make a compiler for. As long as it compiles to the Panacea bytecode, it can be used by an app that embeds the Panacea VM. So, theoretically it could be useful, some day. Mostly, it's just fun to mess around with at the moment, though.
I have another idea that is still in a sort of infant state so I don't want to talk about it too much. It'd be a website/community thingy that would be pretty cool if it doesn't get botched up in the implementation and early stages of use. I'll think more about it and maybe post more if I decide to go ahead with it (or if I decide not to go ahead with it and figure someone else might have a use for the idea).