5.3 Version Control of Generated Code
Do you version your .o ?¬?les? No? Fine, let??™s move on!
As mentioned above, with automatic generation and build you should not need to
version the generated ?¬?les. They are an intermediate product and can always be
reconstructed from the primary source, the models. If, however, your DSM tool does
not ensure correctness or combined versioning of models with their modeling
language and generators, there could still be some scope for doubt. In other words, a
poor DSM tool may not produce the same output twice from the same model: the
modeling language or generators may have changed, even though you took the same
version of the model from version control. In that situation it is important when
versioning the models to include version information of the modeling language and
generators.
In some rare cases, it may also be useful to version the generated code. For instance,
if generation from the DSM tool is time consuming, and there are centralized nightly
builds from hundreds of developers??™ models, caching the generated code can speed
things up. Another case could be where one set of developers builds the models and
generates the output, and a second set takes that output and works with it??”not
changing it, but perhaps writing other code ?¬?les by hand to work with it.
Pages:
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577