Struct fields don't appear until assignment about c0vm-ts HOT 6 CLOSED

I don't think modifying the compiler is the right solution here. I can look at this a bit over break.

from c0vm-ts.

This is an expected behavior. Since the project is actually running compiled bc0 bytecodes behind the curtain (you can see it if you open Settings (little gear on bottom) > Advanced Settings > Expose Bytecode

The compiled bytecode does not contain any type information so I'm doing lots of acrobatics to "reconstruct type" from bytecode and their comments.

While some information (like field name) is available by parsing through the bytecode file directly (regex match on comment), many information like type of field in struct is not available until we actually execute the aaddf pointer arithmetic command on some pointer. Therefore, all the fields that are not touched yet will be invisible from debug console. (We need type information to interpret the binary content in heap and display it properly on debug console!)

(^ This is what heap content looks like under the hood)

This is addressed a little bit, however, by "type reuse" (Settings > Advanced Settings > Experimental - Type Reuse). If you run the code to some intermediate breakpoint and click "Restart", the struct type information (offset, and type of field with that offset) is preserved. In this way, you can see the initial value of fields even before they are touched.

from c0vm-ts.

It is possible, however, to directly parse the C0 source code and figure out the type, offset and name of each field in struct. In fact, such tokenizer & parser for C0 already exists right now (the syntax highlighting is based on it). Maybe, MAYBE, I will try to implement something like this in the future.

from c0vm-ts.

It really sounds like just implementing a tree-walk interpreter (or something else more complex, but that would seem to me to be sufficient) instead of trying to consume bytecode is what needs to be done, at least for the memory diagram relevant featureset.

Even if this is currently the expected behaviour, I would consider this a prerequisite to using this to show examples to students.

from c0vm-ts.

Yeah... That makes sense. Or maybe I can ask iliano to dump more type information in the extended bytecode format (not exposed to students) by changing the behavior of cc0 compiler.

from c0vm-ts.

I'm trying to fix this problem by searching through the syntax tree of source code and extract the type information of structs.

from c0vm-ts.