 |
 |
Articles / TULARC / Operating Systems / VCOMM / |  |
|
|
||||
|
|
|||
|
|
|||
|
||||
|
|
||||
|
   |
|
||
|
10.10: Other Structures |
|
||
|
||||
|
|
|
||
|
||||
|
|
Articles / TULARC / Operating Systems / VCOMM / | |
|
|
||||
|
|
|||
|
|
|||
|
||||
|
|
||||
|
|
|
||
|
10.10: Other Structures |
|
||
|
||||
|
|
|
||
|
||||
|
|
|
|
||
|
||
|
|
|
|
||
|
|
||
|
||
|
|
|
|
||
|
||
This article is from the Programming VCOMM FAQ, by nelson@desktop.nsc.com (Taed Nelson) with numerous contributions by others.
10.10.1: General
Some of the structures have "version" entries, but what version should be
filled in or checked for? Some of this can be inferred from the Serial.vxd
source, but how will developers know if it is updated? This information
should be in the Vcomm.h file.
10.10.2: _COMM_CONFIG
This structure is not documented.
Some its fields can't be understood from the Serial.vxd source. For example,
it seems that the field cc_wVersion is defined with an error in it.
Continue to:
|
|
|
|
 |
|