Quote:
Originally Posted by virtuald
Fair enough. Don't need yet another abstraction for my purposes then. 
|
True - but that also means that you can have multiple implementations behind WPILib. We're actually doing that in the main source code for WPILib, with the actual code and the simulation code. It's cut into three projects - common, simulation, and real, and both the real and simulation project implement some of the classes separately.
Quote:
Originally Posted by virtuald
Yep. Given that they both use the underlying NI chipobject stuff as their interface to the hardware, it's not that surprising that it's similar -- which is why I think it would be easy for anyone wanting to create a HAL to do so. I suspect that the initial implementation of HAL involved cut/paste all the ChipObject stuff from the existing WPILib implementation into the HAL code.
|
Fair enough.
Quote:
Originally Posted by virtuald
The source for HAL is all included in the WPILib source, so that part is covered. I might do a HAL implementation at some point if someone else doesn't do it first. I also have a large backlog, which is why I was hoping someone else had already done it.
|
Well, I don't think they want the WPILib source code public yet - which is the issue, unless you plan to keep you work private for a while.
I'd also consider helping, but I also have a large backlog of pending work.
__________________
Software manager alumnus. Developer of
the CCRE, a powerful robot code framework based on dataflow and composibility.
Refer to as she/her/hers. Years of FRC: 2012, 2013, 2014, 2015, 2016. FLL for a few years beforehand.
Team 1540:
The Flaming Chickens | Portland, Oregon |
Twitter |
Facebook