kcreate / stackvm Goto Github PK

Should include automatic testing of example code and unit tests for each part of the pipeline.

Hello,

First of all, I follow you and wish you very much success for your projects. I really enjoy your ideas behind the projects.

My subject of this issue is, if I am allowed to port this vm to Lua jit with the jvm disabled. I’d like to use lua to address the above challenge cause it’s freaking fast and I think it will work. If I’m allowed, I’ll add you to the license file.

Again, I love your work and I am really engaged for cooperating at jobs in compiler/vm/interpreter funds.

Thanks and regards

Timo S.

For example:

willow% ./bin/stackvm build examples/loops.asm -s -o loops.bc    
Error: sub expected 2 arguments, got 3 at /home/max/Documents/Dev/stackvm/examples/loops.asm:40:3

Hey there,

I know it seem weird, but I have an idea what you could implement on your vm: A thread-safe concurrency Model for the assembler.😂 It would be beneficial for the vm with methods such yielding and threading for implementing programs that run parallel or interrupt each other’s.💡😅

By the way: I am working on a node.js implementation of your stackvm. I have pinned it on my GH profile. It is called ASPL (spelled Aspel) and stands for: adaptive, stack-based, programming, language.

Thanks and regards

Timo

Hy

I’ve got just a little idea to implement: comments and nested comments in the assembler for more readability in the code.😆

Regards

Timo

When I try to compile with make, I get:

willow% make
mkdir -p bin
crystal build src/stackvm.cr -o bin/stackvm --error-trace
Error in src/stackvm.cr:2: while requiring "./command.cr"

require "./command.cr"
^

in src/command.cr:7: while requiring "./monitor.cr"

require "./monitor.cr"
^

in src/monitor.cr:1: while requiring "sdl": can't find file 'sdl' relative to '/home/max/Documents/Dev/stackvm/src'

require "sdl"
^

Makefile:18: recipe for target 'stackvm' failed
make: *** [stackvm] Error 1

• Have a step-by-step tutorial on how to install this
• Example on how to get some assembly running
• How to use the monitor
• How to use the debugger

In it's current state, the code is a huge mess. The assembler should first build the finished executable in memory, without writing anything to disk.

This would allow for lazy symbol resolution.