Language support about ev3dev-lang HOT 3 CLOSED

@bmegli I noticed that you have some enhancements to your R binding in your fork. I'd recommend that you open a PR here to get it merged in to the main repo and then pull over the upstream changes in to your fork so that you have our more recent changes.

One of the things that we have been working on over here is an auto-generation system for our code. Our longer-term goal is to get that implemented in all of our bindings; it enables us to generate the property getters/setters immediately when we change the spec. You might want to try to add it to your bindings; it should make your maintenance job easier.

from ev3dev-lang.

@WasabiFan

Thanks for the info. Made PR.

AutoGen - definitely yes (!), but at a later time. I am considering major shift to the other class system which will change the syntax to C++ bindings like. Then R code and C++ code could be easily mixed using RCPP. R is a total crap when used for real time control, only ok for prototyping and modelling sensors. If syntax is the same the prototype code can be almost directly called as C++ code from R (RCPP).

from ev3dev-lang.

Sounds good.

In your list in the PR description, you mentioned switching to autogen and updating to v0.9.1 as two separate items. Once you implement the autogen system, you'll get most of the updates automatically, because it will be generating based off of the most recent spec version. You will just have to manually add the extra class definitions and associated autogen instructions and all the getters/setters should be generated automatically.

from ev3dev-lang.