Heap-Allocation / Sub-Matrix Handling

[GoogleCodeExporter]

In LinkMechanics every contour and/or frame of the link creates 
direction-matrices for the non-smooth projection (init()-->unknownStage). 
However, only a reference should be enough and is done anyways (e.g. 
updateWRef()). 
Right now a hack (due to empty matrices) seems to solve the problem of 
unnecessary heap-allocation but conceptually this might not be the clean way to 
do it...

Original issue reported on code.google.com by kgrundl on 20 May 2014 at 9:25

[foerg]

Class MechanicalLink has been revised.