The .h files are all written in such a way that any .c file can just
#include <common.h>
or
#include <the-dot-h-of-its-own-type>
without worrying about multiple definitions. As a side effect, common.h
is a canonical list of data type definitions, in the order in which they
have to be known to compile correctly.
At least that's the way they're *supposed* to be written ;-)
73
Frank
AB2KT
Jim Lux wrote:
I've been peering into dttsp.
What would be quite useful is if there were a "dictionary" that said what
each of the 48 modules generically did. Some are obvious (am_demod), some
not so (ovsv). A one or two line description for each one would give you a
good idea where to go hunting when you're looking for a particular routine
or function.
What would also be useful is if there were a table that said which
structure was defined where. You can get a which routine is in which
module from the linker, after a fashion, but the data structures are a bit
more tricky, and since the code makes a lot of use of indirection through
tables, it's hard to follow the nominal flow of control.
James Lux, P.E.
Spacecraft Radio Frequency Subsystems Group
Flight Communications Systems Section
Jet Propulsion Laboratory, Mail Stop 161-213
4800 Oak Grove Drive
Pasadena CA 91109
tel: (818)354-2075
fax: (818)393-6875
_______________________________________________
FlexRadio mailing list
[email protected]
http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz
Archive Link: http://mail.flex-radio.biz/pipermail/flexradio_flex-radio.biz/
FlexRadio Homepage: http://www.flex-radio.com
