> On Aug 22, 2017, at 7:55 AM, Jef Driesen <[email protected]> wrote:
> I don't understand what you gain with those comments. I mean it's just
> comments. Don't you need this kind of info at runtime instead?
Yup - I simply have a tool that parses the source to give me the information
that I want.
> Something like what I proposed for the I/O refactoring:
>
> For the I/O refactoring, I'm already planning to add an extra field with the
> transport type. Since some devices support multiple transports, the transport
> type will need to change into a bitfield. So something like this:
>
> {"Shearwater", "Petrel 2", DC_FAMILY_SHEARWATER_PETREL, 4,
> DC_TRANSPORT_SERIAL | DC_TRANSPORT_BLUETOOTH | DC_TRANSPORT_BLE},
Which doesn't tell me if this is an FTDI chip - which is one of the things that
I need to know.
/D
_______________________________________________
subsurface mailing list
[email protected]
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
