In my previous post, I made the argument for a lot more constructs. But this post is how all those constructs, immutability and flow control will be expressed in EK9.
It might seem strange that I've left the aspect of syntax until t...
In my previous post I covered immutability and touched on the first construct; the constant.
EK9 also has functions, dynamic functions, classes,
dynamic classes and interfaces/traits. These are all unsurprising as they are presented in mos...
In my previous post I dealt with flow control and mentioned immutability.
But why is immutability desirable at all? Why, as developers would we not want to alter/mutate/change variables? After all we need to be able to calculate results an...
In my previous post I outlined the need for a range of new modern types in
In this article I'll discuss the different forms of flow control. I will also introduce a couple of contentious ideas relating to unnecessary complexity in mos...
In my previous post I concluded that both Object Oriented and Function programming should be adopted in
In fact all instances of types in EK9 will be Objects, there will be no primitive types at all. This solves the 'Autoboxing' issue...
In my previous post I came to the conclusion that strong typing should be adopted in EK9.
The next question (before deciding on the types) is to consider the pros-and-cons of Object Oriented programming and Functional programming.