It would be handy to allow included source files (i.e. xml files called using the tag to have some top-level control of the packets / structures defined therein.
I am imagining a scenario where a designer wishes to separate the generated code from each xml file into a separate c/h file pair. Currently this must be specified by setting the file= parameter of each and every packet.
It would be handy to allow included source files (i.e. xml files called using the tag to have some top-level control of the packets / structures defined therein.
I am imagining a scenario where a designer wishes to separate the generated code from each xml file into a separate c/h file pair. Currently this must be specified by setting the
file=
parameter of each and every packet.If the main protocol file is as follows:
Then we could write the sub-files as:
Then (by default) all the dog packets are in
DogPackets.h
- although this can still be overridden on a per-packet basis...