Roborio and Swift?

[Bryan Herbst]

Originally Posted by virtuald

Not true. Any language that can run on linux, could potentially be run on the RoboRIO. The "hard" part (really, it's typically just a lot of tedious work, as opposed to being truly hard) is creating appropriate bindings for WPILib/HAL.

Possibilities include (but are not limited to) Python (done), Ruby, Perl, Go, Javascript, Haskell, Lisp, C#/Mono, D, Brainf*k, LOLCode... whatever someone is willing to put the work into, is possible.

I'd be interested in seeing someone create WPILib bindings for Go or Javascript.

I don't think the comment was about which languages are possible, but rather which languages are probable.

While all the languages you listed can run on the roboRIO, there isn't a great reason to bring most of them to FRC.

I could see arguments in favor of Python and C#, not so much the others. However, because they need to maintain a balance between offering a variety of languages and providing first class support for the available languages, I'm not holding my breath for more officially supported languages.

[virtuald]

Originally Posted by Tanis

I don't think the comment was about which languages are possible, but rather which languages are probable.

While all the languages you listed can run on the roboRIO, there isn't a great reason to bring most of them to FRC.

I could see arguments in favor of Python and C#, not so much the others. However, because they need to maintain a balance between offering a variety of languages and providing first class support for the available languages, I'm not holding my breath for more officially supported languages.

My expectation is that for the forseeable future, FRC will only officially support Java, C++, and LabVIEW.

[Thad House]

Originally Posted by Tanis

I don't think the comment was about which languages are possible, but rather which languages are probable.

While all the languages you listed can run on the roboRIO, there isn't a great reason to bring most of them to FRC.

I could see arguments in favor of Python and C#, not so much the others. However, because they need to maintain a balance between offering a variety of languages and providing first class support for the available languages, I'm not holding my breath for more officially supported languages.

I started working on C# earlier this season. I could access parts of the HAL and DS reporting was working, so it could switch between auto, teleop and disabled, but whenever I tried to open any input or output I would get a segfault. I have a feeling this was because it was using an old version of Mono, which wasnt working correctly with IntPtrs. I think I'm going to need to compile the newest version of Mono to get it working, but I really dont know how to do that, so that will be something to figure out over the summer.

This was good news for most languages though, because if you can interop with C++ libraries, getting basic communication working was really easy, and was done in about a day.