V.1.4 Object-oriented post-processing

In directory “TESTSAT/PYTHON/PROJECTb” one presents an object-oriented post-processing. This project is the translation of the corresponding ruby example presented in chapter X.F.

Significant differences in the programming of the two projects deserve to be noted:

• It seems Python does not allow to define object methods. Therefore, for each object in the ruby project that defines its own methods, one must define an additional class in the Python project.

  For example, the ruby project defines an instance of the “PostCauchy” class called “post_honeycomb”, and the “post_honeycomb” object defines post-processing data in the instance methods. With Python, one first defines a “PostHoneycomb” class that defines the methods used to fill post-processing data. this means that one msut define an additional class.

• In ruby “LoadCases” module, several “proc” objects have been defined. In Python corresponding module, one defines methods corresponding to the “procs”, because the equivalent of ruby proc does not seem to exist in Python. (Python “lambdas” only allow the definition of simple expressions.)