If a debug exception should fire after the execution of an instruction, we should inject the debug exception, which we are not currently doing.

https://howtohypervise.blogspot.com/2019/01/a-common-missight-in-most-hypervisors.html

was just watching the C++ Now presentation on Julia and C++ (https://www.youtube.com/watch?v=hvnxY3NjHQ4) and noticed in the section on Cxx.jl (around 48 minutes in) that there is a special assignment syntax in the REPL ":=" for assigning C++ results back to a Julia variable.

I don't see this documented anywhere here in the docs.

From core's documentation pages there seems to be no obvious link to core's project page to help the reader to obtain the code to actually use it. I'd expect such a link on the front page of the neat documentation site, or on an easy-to-spot page like Getting MNMLSTC Core, or [Download MNMLSTC C

The llvm/clang++ compiler used and provided by mason needs a full XCode installation available. Otherwise you'll hit a warning like:

clang-5.0: warning: no such sysroot directory: '/Library/Developer/CommandLineTools/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk' [-Wmissing-sysroot]

And an error when the program tries to use something from the C standard library. For example:

I get a null pointer exception on line 161 "this->graphics_context._Mypair._Myval2 was nullptr."

auto canvas = graphics_context->create_canvas(size, canvas_flags);

in the window::draw() function

void window::draw()
  {
    graphics::canvas_flags canvas_flags;
    if(flags.test(window_flag::anti_alias))
      canvas_flags |= graphics::canvas_flag::anti_alias;

    auto canvas 

Being able to set not just the color but also the italics or bold behavior of certain syntax terms would be great. If this is already possible it would be great if it could be added to the documentation, as I do not currently see any way to do this.

Need to make test cases for the Compiler and VM to verify their correct functioning, as well as make adding features/modifications easy to test for any breakage in existing system.

The tests must consist of the following components:

• Nil
• Integers
• Floating point numbers
• Strings
• Modules (tests/builtin/mod.fer)
• Language Constructs
  • C

Known already:

• uriparser
• libxspf
• OpenVSP

So the task is finding more and making a list in the readme or so.

May help:
https://github.com/search?q=filename%3Acpptest-output.h&type=Code&utf8=%E2%9C%93

Generating good documentation from source is hard because of the heavy metaprogramming involved. Doxygen assumes that BOOST_HANA_DEFINE_STRUCT is a member function, Sphinx cannot properly process the XML generated by Doxygen.

Possible Solutions:

• Try standardese
• Write Markdown by hand

This should also be automated with Travis. CMake targets