Programming Orientation
-
We started with Procedure Oriented programming. Then we moved on Object Oriented Programming. Now F# is something which is neither OOPs nor POP. What's next and why? :confused: Thanks and Regards Ajit
-
We started with Procedure Oriented programming. Then we moved on Object Oriented Programming. Now F# is something which is neither OOPs nor POP. What's next and why? :confused: Thanks and Regards Ajit
We can not keep clinging to the same thing but keep moving. The world is a vast inn. We are just travellers/visitors and there are a lot of things to visit, see, learn and digest. I admit that you might be attracted by a cool feature in a particular area like F# but be reminded of 'Robert Frost' ("
He gives his harness bells a shake To ask if there is a mistake"). The lines of the poem ("Stopping by woods on snowy evening") should be inspiring us on the desktop always: "The woods are lovely dark and deep, But I have promises to keep, And miles to go before I sleep, And miles to go before I sleep"Vasudevan Deepak Kumar Personal Homepage
Tech Gossips
A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis Levinson -
We started with Procedure Oriented programming. Then we moved on Object Oriented Programming. Now F# is something which is neither OOPs nor POP. What's next and why? :confused: Thanks and Regards Ajit
Yet another programming language? :doh: Do you know about X++[^]? Looks like I need to add F# to the list.
Nobody can give you wiser advice than yourself. - Cicero .·´¯`·->Rajesh<-·´¯`·. Codeproject.com: Visual C++ MVP
-
We started with Procedure Oriented programming. Then we moved on Object Oriented Programming. Now F# is something which is neither OOPs nor POP. What's next and why? :confused: Thanks and Regards Ajit
According to wikipedia, F# mixes functional, procedural and object oriented elements. Advantage: pick the best tool. Disadvantage: to understand someone elses source code, you need to understand all three concepts.
We are a big screwed up dysfunctional psychotic happy family - some more screwed up, others more happy, but everybody's psychotic joint venture definition of CP
blog: TDD - the Aha! | Linkify!| FoldWithUs! | sighist -
According to wikipedia, F# mixes functional, procedural and object oriented elements. Advantage: pick the best tool. Disadvantage: to understand someone elses source code, you need to understand all three concepts.
We are a big screwed up dysfunctional psychotic happy family - some more screwed up, others more happy, but everybody's psychotic joint venture definition of CP
blog: TDD - the Aha! | Linkify!| FoldWithUs! | sighistI have no problem with the concepts, but I do have a problem marrying them to the actual language. I think I just haven't spent nearly enough time with F#.
-
We started with Procedure Oriented programming. Then we moved on Object Oriented Programming. Now F# is something which is neither OOPs nor POP. What's next and why? :confused: Thanks and Regards Ajit
-
I have no problem with the concepts, but I do have a problem marrying them to the actual language. I think I just haven't spent nearly enough time with F#.
Brady Kelly wrote:
I have no problem with the concepts, but I do have a problem marrying them to the actual language.
Yeah. My hesitation comes from the difference of being able to understand the concepts, and working with them fluently - similar to whether I can work out the meaning of a paragraph in a foreign language with the help of a dicitonary and a native speaker, or can read and understand jargon fluently.
We are a big screwed up dysfunctional psychotic happy family - some more screwed up, others more happy, but everybody's psychotic joint venture definition of CP
blog: TDD - the Aha! | Linkify!| FoldWithUs! | sighist -
We started with Procedure Oriented programming. Then we moved on Object Oriented Programming. Now F# is something which is neither OOPs nor POP. What's next and why? :confused: Thanks and Regards Ajit
combination of the two paradigms. It will be known as POOP. Programming with Objects and Other Pieces. :)
Chris Meech I am Canadian. [heard in a local bar] Donate to help Conquer Cancer[^]
-
We started with Procedure Oriented programming. Then we moved on Object Oriented Programming. Now F# is something which is neither OOPs nor POP. What's next and why? :confused: Thanks and Regards Ajit
Ajit Shekhawat wrote:
What's next and why?
whatever gets the job done the quickest. because that's what programming is for.
-
combination of the two paradigms. It will be known as POOP. Programming with Objects and Other Pieces. :)
Chris Meech I am Canadian. [heard in a local bar] Donate to help Conquer Cancer[^]
In which case, let me be the first to coin the phrase IronPoop - Poop running on the DLR :)
-
combination of the two paradigms. It will be known as POOP. Programming with Objects and Other Pieces. :)
Chris Meech I am Canadian. [heard in a local bar] Donate to help Conquer Cancer[^]
The future is going to be full of POOP. Look forward to see things like Open POOP, POOP .NET, POOP Studio, etc.,
Nobody can give you wiser advice than yourself. - Cicero .·´¯`·->Rajesh<-·´¯`·. Codeproject.com: Visual C++ MVP
-
In which case, let me be the first to coin the phrase IronPoop - Poop running on the DLR :)
Good thing - Ruby on POOP.
Nobody can give you wiser advice than yourself. - Cicero .·´¯`·->Rajesh<-·´¯`·. Codeproject.com: Visual C++ MVP
-
We started with Procedure Oriented programming. Then we moved on Object Oriented Programming. Now F# is something which is neither OOPs nor POP. What's next and why? :confused: Thanks and Regards Ajit
Ajit Shekhawat wrote:
Now F# is something which is neither OOPs nor POP.
Functional.
Ajit Shekhawat wrote:
What's next and why?
A combination of the above. You see this with functional features being added to C#. Many different programming approaches seem to have reached equal footing now; there's not just one dominant paradigm. So it's up to a programmer to become intimately familiar with his/her domain. Then choose the most appropriate tools for getting the job done in that domain.
-
Good thing - Ruby on POOP.
Nobody can give you wiser advice than yourself. - Cicero .·´¯`·->Rajesh<-·´¯`·. Codeproject.com: Visual C++ MVP
... and don't forget the Mac version iPOOP
:..::. Douglas H. Troy ::..
Bad Astronomy |VCF|wxWidgets|WTL -
combination of the two paradigms. It will be known as POOP. Programming with Objects and Other Pieces. :)
Chris Meech I am Canadian. [heard in a local bar] Donate to help Conquer Cancer[^]
in addition to the ironPoop listed above I formally dedicate these to the new POOP standard: FlexPOOP : cross platform POOP barePOOP/miniPOOP/microPOOP : reduced footprint embedded systems POOP (and a variation on the last one there: uPOOP) for the computer aided code writing folks there is: POOPaware, EnterprisePOOP, and distributedPOOP for the large cluster folks: distributedPOOP, clusterPOOP, NetPOOP (not to be confused with POOP.NET), and GridPOOP but always remember, no matter where you POOP, always verify your error checking is done correctly! Throw POOP, and Catch POOP! Now go forth brave programmers of the future and POOP in everyway you can!
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
We started with Procedure Oriented programming. Then we moved on Object Oriented Programming. Now F# is something which is neither OOPs nor POP. What's next and why? :confused: Thanks and Regards Ajit
Ajit Shekhawat wrote:
Programming Orientation
Landscape.... think on it a bit...
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
Ajit Shekhawat wrote:
Now F# is something which is neither OOPs nor POP.
Functional.
Ajit Shekhawat wrote:
What's next and why?
A combination of the above. You see this with functional features being added to C#. Many different programming approaches seem to have reached equal footing now; there's not just one dominant paradigm. So it's up to a programmer to become intimately familiar with his/her domain. Then choose the most appropriate tools for getting the job done in that domain.
Leslie Sanford wrote:
You see this with functional features being added to C#.
and C++0x
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
in addition to the ironPoop listed above I formally dedicate these to the new POOP standard: FlexPOOP : cross platform POOP barePOOP/miniPOOP/microPOOP : reduced footprint embedded systems POOP (and a variation on the last one there: uPOOP) for the computer aided code writing folks there is: POOPaware, EnterprisePOOP, and distributedPOOP for the large cluster folks: distributedPOOP, clusterPOOP, NetPOOP (not to be confused with POOP.NET), and GridPOOP but always remember, no matter where you POOP, always verify your error checking is done correctly! Throw POOP, and Catch POOP! Now go forth brave programmers of the future and POOP in everyway you can!
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
LOL. Sometimes I think I missed my calling. What I could've accomplished if only I had gone into marketing. :)
Chris Meech I am Canadian. [heard in a local bar] Donate to help Conquer Cancer[^]
-
in addition to the ironPoop listed above I formally dedicate these to the new POOP standard: FlexPOOP : cross platform POOP barePOOP/miniPOOP/microPOOP : reduced footprint embedded systems POOP (and a variation on the last one there: uPOOP) for the computer aided code writing folks there is: POOPaware, EnterprisePOOP, and distributedPOOP for the large cluster folks: distributedPOOP, clusterPOOP, NetPOOP (not to be confused with POOP.NET), and GridPOOP but always remember, no matter where you POOP, always verify your error checking is done correctly! Throw POOP, and Catch POOP! Now go forth brave programmers of the future and POOP in everyway you can!
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
And not forgetting EmbeddedPOOP featuring a cut down version of the POOP Runtime (Runny POOP) :)
-
We started with Procedure Oriented programming. Then we moved on Object Oriented Programming. Now F# is something which is neither OOPs nor POP. What's next and why? :confused: Thanks and Regards Ajit
Ajit Shekhawat wrote:
Now F# is something which is neither OOPs nor POP. What's next and why?
F# is a functional programming language. I heard about it a couple of years back (someone from our organization mentioned that they are planning to use it - I don't know whether they are using it now). Functional programming languages are the new frontier for many of the people. People say that with more work is going to be done at 'parallel programming' because of the advancement in hardware (multi-core CPUs etc), functional programming languages are better suitable to do those types of tasks. Haskell, Erlang are also getting more attention these days.