There were some areas where I had requested feedback. Based on the feedback received from external and internal patrons these are the decisions.

Function overloading

            Our proposed approach, in nut shell, was to create an additional parameter whenever overload conflicts arise. Many of the readers and internal supporters found our approach not very clean because there were a lot of ways to modify a method from the diagram and adding a parameter of a random type to resolve the conflict will make the users uncomfortable. Based on the feedback and with the intention of keeping things simpler we have decided to make the designer not allow creation of overloaded conflicts. We will trap an overload conflict and will let the user know that an overload conflict occurred and so the method creation will not be allowed.

Inline

            Again based on precious feedback we will make the inline read/write. You will be able to set the Inline property (bool) on a method which is defined outside the class. This will add the “inline” keyword. If the function is defined inside the class, then we will make the property readonly.

Constant Kind