Modeling: User's Guide

Previous: 3.1.2.2 Dynamic generation using Up: 3.1 From model to Next: 3.2 The framework's requirements

---

 
3.1.3 Static vs. dynamic: what's best?

The question of which option one should use is an opened question! In fact, it highly depends on your own preferences: some people do not want to hear of code generators, others keep metaclasses away from their code. Some argue that it is best to maintain the model only, deriving the necessary modules at runtime, while others prefer to statically generate the code so that it can be put under version control, for example, or because they want to keep an eye on the generated parts.

This being said, here are a few comments:

• if you go for the static generation of python code, better choose the ``base'' scheme if you use the script mdl_generate_python_code.py (or a similar approach if you build the code by your own means).

• whichever method you choose, static generation, dynamic build with or without metaclasses, it is ``officially'' supported. Some people have argued that having all these possible ways available makes it difficult to make a choice; our position is that since we are here speaking about the code people write, we shouldn't force anyone to follow a given path if they prefer the other one. We think (and hope!) that the offered possibilities cover most code pratices -if you think we forgot something, we'll be happy to hear from you.

  Now if you're really looking for an advice, let's say that our personal preference consists in dynamically building the modules, using metaclass and properties.

---

Modeling: User's Guide

Previous: 3.1.2.2 Dynamic generation using Up: 3.1 From model to Next: 3.2 The framework's requirements

---

Release 0.9, documentation updated on March 4, 2006.

Comments are welcome: Sebastien Bigaret / Modeling Home Page
Hosted by: