kondrak/codespawn

Code generator written in Rust

Hi! 👋

I'm a programmer working in games and entertainment industry. I currently focus on creating tech that makes game development possible, such as engines and tools that simplify people's work. My primary programming languages are C, C++ and Rust.

codespawn's Issues

Issue with structs in C

Currently in ProDBG there is a struct being generated like this

struct PDVec2 {
    float x;
    float y;
};

And used like this

struct PDUI {
    ...
    PDVec2 (*get_window_size)();
}

This doesn't work as C has to have one of these options

1:

typedef struct PDVec2 {
    ...
} PDVec2;

2:

struct PDUI {
    struct PDVec2 (*get_window_size)();
}

Return value handling

Consider using Result<> for return values for better error handling.
Further read: https://doc.rust-lang.org/book/error-handling.html

Bug when processing multiple config files

settings get overwritten

Add funcptr tag

Treating func as funcptr is currently troublesome.

Alternative definition of variable/function name and type

 { "void": "text_colored_v", 
   "var": [ { "const PDColor": "col" }, { "const char*": "fmt" }, { "va_list": "args" } ]
 }

Consider alternative to avoid explicit type, name attributes and compress it so it takes less space in JSON.

ignore typeless variables and funcs

don't take them into consideration if type is overriden to empty

Support multiple attribute tags

Simplify config tag

It doesn't need anything else except file name, so can be simplified for JSON

Own error type for better chaining of panics/errors

...and use try! everywhere, avoid unwrap()

Consider Lua as API definition format

Indentation support

Add a language specific field in configs that will determine whether we want to use tabs/spaces and how many chars should be applied.

add Rust bitfield support

will generate bitfield! in Rust and a standard enum in C++

Question about qemu

Would it be possible to apply this to qemu to generate bindings? Qemu's qapi is a json like specification which my qapi parser can turn into valid json. I've been playing around with making bindings and the challenging part is getting the code generation correct.

Support for optional values in Rust