Java is one of the imperative programming languages, like most popular programming languages. What I write in Java methods strive for is to avoid any side effects, ie, a method used only the transfer parameters. This greatly increases the readability and maintainability of the code. So you can declare such methods as static. This method relates not to object but to the class. It could be used The method also move to any place, of which I advise in general because this is the understanding of the code would be detrimental. I call this type of programming neoprozedurale programming. When following this simple paradigm, it will be seen that both the Code and the mindset of the programmer a positive change. If one neglects the transport aspect of Web services, then the neoprozedurale programming is reminiscent of the web service idea. If one then combines the neoprozedurale programming with test-driven programming, functional programming is one of the closer. But functional programming is more. A light, practical guide provides in blog Alexander Pohl N N blog. What a great name for a blog, I'm envious that such a name is not even occurred to me. What question I ask myself, is the functional programming, a goal of agile software development? I hear the slander HASKELL programming in the past. And the Java and C programmers are complaining about the waste of space (Sorry, stack overflow: use the-Xss) and computing time, if we replace loops by recursion. I can, of course, the optimization of ion exchange Endre (Tail Recursion) as against, but I do not know whether Java (compiler, JVM) makes such optimizations. I'm not quite sure what is the current state of Java, but it is at OpenJDK (Da Vinci Machine) on the plan ( Link ). I'm curious to see how it goes. I would like to put in a kind of functional Java compiler mode to program in Java functional.
0 comments:
Post a Comment