ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Computers do run with procedures and not objects, after all, which is another reason I don't like Java.
I think that is missing the point; in that most of the world consists of objects and not clean and tidy procedures. Thus when modelling problems that can be more easily expressed in terms of objects then an O-O language will work and it is the language that then does the transformation from objects to the computers preference of procedures.
Oh, what I meant was 'if...else', do..while,etc... those things are similar to logical reasoning or problem solving.
I would say that what you are suggesting is perfectly valid. However, there are other equally valid ways of looking at programming.
Personally, I would like to see problem solving removed from the idea of programming. Simplistically speaking programming is just syntax and semantics. Problem solving is with analysis, and I believe that they (programming and analysis) should be separated, the divide will be a fuzzy one but it is good to try and keep them apart.
It used to scare me too - until I realized I was doing it in Perl already.
Actually, I've been also pushed too functional programming by my VLSI background - in VLSI one has state elements and combinational logic - the latter is kind of functions in functional programming.
The clear separation into stateless functions and state is _the_ thing allowing to formally verify/prove correctness.
And, as I read about OCaml, performance shines where the compiler is able after all these formal transformations due to clear separation and state to well optimize the code - sometimes better than a C++ compiler.
And, as I read about OCaml, performance shines where the compiler is able after all these formal transformations due to clear separation and state to well optimize the code - sometimes better than a C++ compiler.
I've heard OCaml is high performance as well, and it has an interpreter so you can test code before compiling. Very cool. Unfortunately, I find the OOP syntax quite heavy. Something like printf.printf.printf.printf().
I've heard OCaml is high performance as well, and it has an interpreter so you can test code before compiling. Very cool. Unfortunately, I find the OOP syntax quite heavy. Something like printf.printf.printf.printf().
OCaml does nto force you to use OOP - actually, any OCaml tutorial starts without any OOP whatsoever.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.