Functional sensor/actuator interfaces

harfordflyer / grtframework

Automatically exported from code.google.com/p/grtframework

0 stars 0 forks source link

Functional sensor/actuator interfaces #11

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago

When more than 1 class specify a single functional piece of hardware 
(GRTCANJaguar/GRTJaguar/GRTVictor), it becomes messy to switch between them 
when necessary. This is particularly true and relevant for sensors, where the 
event framework may better be suited for functional sensor abstractions.

Original issue reported on code.google.com by andrewth...@gmail.com on 20 Jun 2011 at 10:31

GoogleCodeExporter commented 8 years ago

Original comment by andrewth...@gmail.com on 20 Jun 2011 at 10:32

Added labels: Type-Enhancement
Removed labels: Type-Defect

GoogleCodeExporter commented 8 years ago

Original comment by andrewth...@gmail.com on 20 Jun 2011 at 10:51

Changed state: New

GoogleCodeExporter commented 8 years ago

Technically, none of those ought to represent the same piece of hardware, but 
it is certainly valid to say that they represent hardware with similar 
functionality. While in principle Mechanisms abstract this, it may be nice to 
provide functional interfaces. This creates some grey areas, but...

Original comment by sparta...@gmail.com on 25 Jun 2011 at 8:15